To-do Fixer
to-do-fixer executes directory-backed tasks in fresh Codex sessions. It
selects pending files randomly and processes them one at a time until the
directory is empty or Codex reports a global usage or authentication limit.
Requirements
- Python 3.10 or newer
- Git
- An installed and authenticated
codexCLI - Local GitHub repository clones beneath the selected repository root
Installation
From this directory:
python3 -m pip install .
Task format
Each non-hidden regular file directly inside the task directory is a pending
task. The first line is the GitHub repository in OWNER/REPO format. Every
remaining byte of UTF-8 text is used as the Codex prompt.
kaizten/example-repository
Implement the requested feature, run its tests, and update the documentation.
Repository clones are identified from their GitHub origin remote rather than
from their directory name. A missing clone or multiple matching clones causes
that task to fail.
Usage
to-do-fixer ~/codex-tasks
Repositories are searched recursively beneath ~ by default. Select another
root with:
to-do-fixer ~/codex-tasks --repos-root ~/workspaces
Codex runs sequentially with the workspace-write sandbox and
--approve-for-me. A structured final response is required before a task is
considered complete.
Completed tasks move into done/. Invalid, missing, ambiguous, blocked, or
otherwise failed tasks move into failed/. Existing files in either directory
are never overwritten. If Codex reaches a usage, quota, rate, credit, or
authentication limit, the current task remains pending and the command stops.
Only one to-do-fixer process may use a task directory at a time. Pressing
Ctrl-C stops the active Codex process and leaves its task pending.
Exit codes
| Code | Meaning |
|---|---|
0 |
Every pending task was processed. Some may have moved to failed/. |
1 |
Startup or configuration failed. |
2 |
A global Codex limit or authentication failure stopped processing. |
130 |
The user interrupted processing. |
Development
python3 -m unittest discover -s tests -v
./build-package.sh
Metadata
Release files for to-do-fixer 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| to_do_fixer-0.0.1.tar.gz | 8.9 kB | Without provenance | Details for to_do_fixer-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| to_do_fixer-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for to_do_fixer-0.0.1-py3-none-any.whl |
Total release size: 15.7 kB
Release files / to_do_fixer-0.0.1.tar.gz
| Download URL | to_do_fixer-0.0.1.tar.gz |
|---|---|
| Size | 8.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
134b7823f232a87470d0bb1796c3b42a18d98c3d3e6c6b6a23fa640b7cd8a82c
|
|
BLAKE2b-256 checksum How to use checksums |
9f376bd218b6454d8d1e7885e083e27b6e8fbed148ae38d556e829aa3e745fdf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / to_do_fixer-0.0.1-py3-none-any.whl
| Download URL | to_do_fixer-0.0.1-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b41ba63e7fdfdf3834a0f2708888e92b2d914275996c4aa1083f4913542173c8
|
|
BLAKE2b-256 checksum How to use checksums |
aaa8db04710956ecf98de30b1fdce8d49c2e8a96ea3bfd295220291ebdd95ae7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for to-do-fixer 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.