implement
Skill421 starsChanged 19 days agoApache-2.0View on GitHub
Implement a celestia-app code change with the safety workflow - triage, align, implement, invariant review loop, verify. Use when the engineer confirms the invariant workflow at the interactive gate or invokes /implement directly.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- chuckplayer/claude-agent-packtheir own version, first seen Nov 16, 2026
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- geoffbremner/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use setup-ts-deep-modules, ask-matt and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
liufeng1976Skillsetup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.
Also in 48 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 104 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 56 projects that use this
richard12511Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 48 projects that use this
AWSSkillto-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Also in 100 projects that use this
GoogleSkillto-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Also in 180 projects that use this
- +2 more from google
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- mattpocock/skills★ 325ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- foambubble/foam★ 17ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.6ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- fallow-rs/fallow★ 5.4ksame name
- withcoral/coral★ 5ksame name
- bestofjs/bestofjs★ 3.1ksame name
182 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- recoverySkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
4
Distinctive
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 18
When in doubt, treat as the higher tier.
- Very specific: line 24
Write an assumptions note to docs/plans/<task>.md: goal, stated assumptions, invariants in play (by INV number), design decisions, open …
- Distinctive: line 29
Write the smallest diff that solves the problem.
- Very specific: line 30
Run make build after Go changes.
- Distinctive: line 39
Stop when a round produces zero confirmed findings, or after three rounds total.
- Distinctive: line 44
Run the tests covering the changed behavior.
“Common” is measured: kept by at least 6 in 10 of the 175 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/implement — safe code generation workflow
Implement the requested change by following these phases in order. Read docs/ai/invariants.md before anything else.
Phase 0 — Triage
Determine the risk tier from the files the change will touch:
- Risky: anything under
x/,app/,pkg/,proto/, ormultiplexer/. - Light: docs, test-only changes, scripts, tooling,
.github/. - Consensus-critical: risky, and the diff changes a state transition reachable from ABCI — message servers in
x/*/keeper, ante decorators,PrepareProposal/ProcessProposal/FinalizeBlocklogic, square construction, migrations, upgrade handling.
When in doubt, treat as the higher tier. Light tier: skip Phase 1 and Phase 3 entirely — implement, then run Phase 4. If the diff grows into a risky path mid-task, re-triage and ask the engineer again.
Phase 1 — Align (risky only, hard gate)
- Explore the code involved. Answer every question the codebase can answer before asking the engineer.
- Interview the engineer about every unclear or under-defined aspect. Give a recommended answer for each question.
- Write an assumptions note to
docs/plans/<task>.md: goal, stated assumptions, invariants in play (by INV number), design decisions, open questions, and an implementation plan (ordered steps, files to touch, tests to add — as short as the task allows). Never commit this file. - Present the note and wait for explicit confirmation. Do not write code before the engineer confirms.
Phase 2 — Implement
- Write the smallest diff that solves the problem. Follow existing patterns in the repo.
- Run
make buildafter Go changes. - For bug fixes: write the reproducing test first, watch it fail, then fix.
Phase 3 — Review loop
- Get the full diff (
git diffplus untracked files) and spawn these agents from.claude/agents/in parallel on it:determinism-reviewer,adversarial-input-reviewer,consensus-reviewer,compat-reviewer,simplicity-reviewer. Give each the diff and the path to the assumptions note if one exists. If your tool can't load these agents, use each.claude/agents/<name>.mdas a review checklist yourself. - Consensus-critical tier: also spawn
adversarial-reviewerin the first round. In later rounds, re-run it only on state transitions whose code changed during fixes. The engineer can request it for any change or skip it for a provably trivial one; record a skip in the report. - For every finding, spawn a
finding-verifieragent to try to refute it. Discard refuted findings. Escalate unproven findings to the engineer — never fix them on your own. - Fix all confirmed findings, then run the reviewers again on the full current diff, pointing them to what changed during fixes.
- Stop when a round produces zero confirmed findings, or after three rounds total. Escalate any still-open findings to the engineer — never silently drop them.
Phase 4 — Verify
make lintandmake test-shortmust pass.- Run the tests covering the changed behavior; add tests where behavior changed.
Phase 5 — Report
Summarize for the engineer: what changed and why, assumptions honored, findings fixed vs escalated, and a one-line status per invariant (respected or not applicable).
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.

