implement
Skill1 starsChanged yesterdayMITView on GitHub
Implement a spec or ticket, or address review findings on its existing pull request.
193 other projects use a version of this, 61 of them edited.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatoredited, 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/skillsedited, first seen Nov 15, 2026
- SireJeff/k0ntexttheir own version, first seen Nov 15, 2026
Used with
Projects with it also use setup-ts-deep-modules, ask-matt and 7 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 43 projects that use this
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 91 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 50 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 88 projects that use this
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 42 projects that use this
GoogleSkillresolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
Also in 83 projects that use this
Other versions193 projects use a version of this.
Word for word · 1
- lutzseverino/repo-standards★ 0100% same
Edited · 61
- mattpocock/skills★ 325k14% same
- QuivrHQ/quivr★ 40k22% same
- The-Vibe-Company/quivr★ 40k22% same
- formbricks/formbricks★ 13k14% same
- ArcReel/ArcReel★ 6.6k14% same
- withcoral/coral★ 5k14% same
- bestofjs/bestofjs★ 3.1k22% same
- moeru-ai/xsai★ 66722% same
- aws/graph-explorer★ 49222% same
- biersoeckli/QuickStack★ 36514% same
51 more not listed
Wrote their own version · 131
- foambubble/foam★ 17ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.8ksame name
- fallow-rs/fallow★ 5.4ksame name
- meta-pytorch/OpenEnv★ 2.9ksame name
- huggingface/OpenEnv★ 2.9ksame name
- oxsecurity/megalinter★ 2.7ksame name
- muxy-app/muxy★ 2.4ksame name
- pymc-labs/pymc-marketing★ 1.3ksame name
- adobe/S3Mock★ 1.2ksame name
- nodetool-ai/nodetool★ 637same name
121 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- babysitSkill
- codebase-designSkill
- code-reviewSkill
- create-adopted-repoSkill
- create-repositorySkill
- diagnosing-bugsSkill
- domain-modelingSkill
- factorySkill
- grillingSkill
- grill-with-docsSkill
- improve-codebase-architectureSkill
- orchestrateSkill
- prototypeSkill
- prSkill
- repository-standardsSkill
- researchSkill
- retroSkill
- reviewSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wayfinderSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 175 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Before editing, read CONTRIBUTING.md for the repository's branch and validation requirements.
- Distinctive: line 10
When the input is review findings on an existing pull request, read the findings and continue on that pull request's branch.
- Distinctive: line 15
Use /tdd where possible, at pre-agreed seams.
- Distinctive: line 17
Run typechecking regularly, single test files regularly, and the repository's required validation on the final commit.
- Very specific: line 20
Before delivery in a factory repository, read the installed factory-workflow rules' Run kinds section and .scriptorium/config.json's …
- Very specific: line 25
Before reporting success, satisfy CONTRIBUTING.md's Worker handoff condition and include its head, trusted required-check authority, …
- Very specific: line 35
Before reporting success, satisfy CONTRIBUTING.md's Worker handoff condition.
- Distinctive: line 51
When it is missing, follow the contribution guide's comment requirements.
- Distinctive: line 54
When it is missing, use the draft handoff above.
- Distinctive: line 56
When it is missing in a factory repository, no review run is configured.
“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
A prompt or brief naming this skill is its invocation.
Before editing, read CONTRIBUTING.md for the repository's branch and
validation requirements. Implement the work described in the spec or tickets.
When the input is review findings on an existing pull request, read the
findings and continue on that pull request's branch.
Apply codebase-design's Ownership check to the change, including its contract-disagreement route.
Use /tdd where possible, at pre-agreed seams.
Run typechecking regularly, single test files regularly, and the repository's required validation on the final commit.
Before delivery in a factory repository, read the installed factory-workflow
rules' Run kinds section and .scriptorium/config.json's runKinds. When no
review run is configured, commit and push the work, write the PR body with
pr, open a ready pull request (or mark its existing draft ready), and invoke
babysit to deliver it under those rules, including any prescribed worker handoff.
Before reporting success, satisfy CONTRIBUTING.md's Worker handoff condition
and include its head, trusted required-check authority, check-location, command
and outcome record.
That route retains babysit's applicable internal reviews and merge conditions.
Otherwise, for new work, commit and push the branch, write the body with pr,
and open one draft pull request as CONTRIBUTING.md directs. For review findings,
commit and push the fixes to the same pull request and leave it a draft;
before replying to findings, read the installed comments rules' Review-thread
replies section and answer there as it directs.
Before reporting success, satisfy CONTRIBUTING.md's Worker handoff condition.
Report the pull request and its required head, trusted required-check authority,
check-location, command and outcome record, then stop. Leave review, marking ready,
babysitting and merging to the separate agent running review; do not run a
self-review.
<!-- Seam (deferred): Scriptorium configuration reads; consumers: 6; extraction proposed in https://github.com/lutzseverino/repo-canon/issues/967. -->Reads
Paths are relative to the repository root.
CONTRIBUTING.md: branch, validation and pull request requirements. When it is missing, work on a branch dedicated to the change, run the available checks, and open a draft pull request withpras above..repo-standards/rules/comments.md: how to reply to review findings. When it is missing, follow the contribution guide's comment requirements; without either source, report the fixes in the handoff..repo-standards/rules/factory-workflow.md: the factory's delivery route. When it is missing, use the draft handoff above..scriptorium/config.json: the configured review run underrunKinds.review. When it is missing in a factory repository, no review run is configured; follow the installed factory rules' delivery route.- The
codebase-designskill: the check applied above. When missing, report the gap through the contribution guide's Findings route, or in the handoff when the guide is missing; retain the recorded contract.
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.

