accelerator / tasks
CLAUDE.md34 starsChanged 51 days agoMITView on GitHub
- pyrefly and ruff are version-pinned exactly in pyproject.toml because their rule sets are version-sensitive. Shared helpers live in tasks/shared/. - Release/version logic enforces version coherence: plugin.json, the cli/ workspace Cargo.toml, and any version-pinned member manifest must agree. cli/Cargo.lock counts too — it carries a copy of the version per workspace member, so version.write syncs it via cargo metadata (the minimal update, never generate-lockfile). Clippy runs --locked, so drift there surfaces as an unrelated-looking Rust failure; tests/unit/tasks/test_version.py guards it by…
In this repository38 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- hooks/CLAUDE.mdCLAUDE.md
- clean-commentsSkill
- raise-prSkill
- configureSkill
- initSkill
- migrateSkill
- pathsSkill
- create-adrSkill
- extract-adrsSkill
- review-adrSkill
- analyse-design-gapsSkill
- inventory-designSkill
- describe-prSkill
- respond-to-prSkill
- review-prSkill
- create-noteSkill
- create-planSkill
- implement-planSkill
- review-planSkill
- stress-test-planSkill
- validate-planSkill
- conduct-spikeSkill
- research-codebaseSkill
- research-issueSkill
- research-topicSkill
- commitSkill
- visualiseSkill
- create-work-itemSkill
- extract-work-itemsSkill
- list-work-itemsSkill
- refine-work-itemSkill
- rekey-work-itemsSkill
- review-work-itemSkill
- stress-test-work-itemSkill
- sync-work-items-recoverySkill
- sync-work-itemsSkill
- update-work-itemSkill
The file
Files
Build system
- pyrefly and ruff are version-pinned exactly in
pyproject.tomlbecause their rule sets are version-sensitive. Shared helpers live intasks/shared/. - Release/version logic enforces version coherence:
plugin.json, thecli/workspaceCargo.toml, and any version-pinned member manifest must agree.cli/Cargo.lockcounts too — it carries a copy of the version per workspace member, soversion.writesyncs it viacargo metadata(the minimal update, nevergenerate-lockfile). Clippy runs--locked, so drift there surfaces as an unrelated-looking Rust failure;tests/unit/tasks/test_version.pyguards it by name instead. - Registering a new dispatched sub-binary is a fourteen-point surface — see
tasks/README.md#registering-a-dispatched-sub-binarybefore adding one. Registering a plain library crate is a smaller surface — seetasks/README.md#registering-a-library-crate. Adding a subcommand to an existing sub-binary is smaller still — seetasks/README.md#adding-a-subcommand-to-an-existing-sub-binary.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

