team-fix
Skill11 starsChanged 4 months agoMITView on GitHub
Use for the full bug-fix pipeline only on explicit request. Never infer from an ordinary bug fix. Runs the compressed pipeline.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-team-skillSkill
- version-bumpSkill
- team-code-reviewSkill
- team-designSkill
- team-implementSkill
- team-migrateSkill
- team-planSkill
- team-prSkill
- team-questionSkill
- team-researchSkill
- team-security-reviewSkill
- teamSkill
- team-structureSkill
- team-updateSkill
- team-worktreeSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Before each consuming step, read its linked shared rules from this installed skill directory.
- Distinctive: line 11
If a required read fails, stop that step with the exact path.
- Very specific: line 17
Run WORKTREE → REPRODUCE → RED → GREEN → VERIFY → SHIP in order.
- Very specific: line 19
After Worktree, run each step in its own fresh subagent per Execution's ## Step dispatch.
- Distinctive: line 23
Read each reference completely when reaching it, in order.
- Distinctive: line 36
Read and apply: bug fix rules and execution rules.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Team Fix — Bug Fix Pipeline
Before each consuming step, read its linked shared rules from this installed skill directory. If a required read fails, stop that step with the exact path. Never use checkout fallback or recursive loading.
Invocation follows human control rules: fire only on stated pipeline intent; a plain "fix this bug" asks for an inline fix.
Core contracts
- Run
WORKTREE → REPRODUCE → RED → GREEN → VERIFY → SHIPin order. - For a ticket, read tracking rules; move it to in-progress before work, and to in-review only after its draft PR becomes ready.
- After Worktree, run each step in its own fresh subagent per Execution's
## Step dispatch; keep gates, aborts, and ticket moves inline.
Procedure references
Read each reference completely when reaching it, in order; later stages depend on earlier state and gates.
- Input
- When to Use
- Pipeline
- Setup
- Worktree
- Execution
- Ship
- Aborting
Applied principles
Read and apply: bug fix rules and execution rules.
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.