reimre
Skill0 starsChanged 32 days agoMITView on GitHub
End-to-end wrapper running research-and-implement then review-pipeline on a GitHub issue, carrying it from investigation through the user-controlled merge gate.
In this repository33 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- authoritative-text-rulesSkill
- breachreaperSkill
- bug-to-contractSkill
- code-review-gateSkill
- codex-contract-test-reviewSkill
- codex-plan-reviewSkill
- codex-reviewSkill
- copilot-reviewSkill
- debtreaperSkill
- diff-rootSkill
- docreaperSkill
- done-checkSkill
- driftreaperSkill
- file-adrSkill
- file-issueSkill
- file-pubdocSkill
- file-pullreqSkill
- finding-to-auditSkill
- finding-triageSkill
- gate-miss-to-issueSkill
- gh-body-auditSkill
- gh-body-conventionsSkill
- implementSkill
- land-via-integration-branchSkill
- quality-listSkill
- read-issueSkill
- research-and-implementSkill
- researchSkill
- review-pipelineSkill
- review-telemetrySkill
- stage-commit-pushSkill
- todo-checkSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Do not inline their steps, diagrams, or rule lists — they drift when the sub-skill is updated.
≈ “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
reimre
End-to-end wrapper.
Runs research-and-implement then review-pipeline back to back.
Issue: #$ARGUMENTS
Flow
- Phase A — invoke
research-and-implement $ARGUMENTS. Branch baseline, root baseline, research, and implementation are handled there. Skip/implement's terminal/done-check— Phase B owns the audit. - Phase B — invoke
review-pipeline, supplying the root Phase A settled.
Sub-skill internal phases are referenced by name only. Do not inline their steps, diagrams, or rule lists — they drift when the sub-skill is updated.
Stop points
Inherits review-pipeline's stop points unchanged — notably the user-controlled merge gate between Phase 4a and Phase 4b.
Do not auto-merge.
Plan approval inside /research is also unchanged.
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.