implementation
Skill902 starsChanged 53 days agoApache-2.0View on GitHub
Implement the requested changes. Write production-ready code, follow existing patterns, and use proportionate verification.
18 other projects use a version of this.
Adopted by
Most recently taken up by
- GravionLabs/skillstheir own version, first seen Nov 15, 2026
- scolladon/crafttheir own version, first seen Nov 15, 2026
- thunderstormwang/AgentSkillstheir own version, first seen Nov 6, 2026
- Zejnilovic/agdtheir own version, first seen Nov 1, 2026
- jackstine/forgectltheir own version, first seen Nov 1, 2026
- grace-method/grace-plugintheir own version, first seen Oct 25, 2026
Used with
Projects with it also use bug-fix, playwright-cli and 2 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.
u9401066Skillbug-fix
Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.
Also in 3 projects that use this
MicrosoftSkillplaywright-cli
Automate browser interactions, test web pages and work with Playwright tests.
Also in 4 projects that use this
SentrySkillreview
Fixture review skill.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 4 projects that use this
Other versions18 projects use a version of this.
Word for word · 1
- ceedaragents/cyrus★ 888100% same
Edited · 0
None found.
Wrote their own version · 17
- bholmesdev/hubble.md★ 1.5ksame name
- EmeaAppGbb/spec2cloud★ 100same name
- jackstine/forgectl★ 8same name
- Zejnilovic/agd★ 5same name
- crgarcia12/Liliput★ 4same name
- websublime/mister-anderson★ 3same name
- jvalin17/agent-toolkit★ 2same name
- scolladon/craft★ 2same name
- JosefGisis/skills★ 1same name
- grace-method/grace-plugin★ 0same name
7 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 repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- packages/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- googleSkill
- release-core-testSkill
- cyrus-setup-claude-authSkill
- cyrus-setup-endpointSkill
- cyrus-setup-githubSkill
- cyrus-setup-gitlabSkill
- cyrus-setup-launchSkill
- cyrus-setup-linearSkill
- cyrus-setup-prerequisitesSkill
- cyrus-setup-repositorySkill
- cyrus-setupSkill
- cyrus-setup-slackSkill
- debugSkill
- f1-test-driveSkill
- investigateSkill
- releaseSkill
- summarizeSkill
- verify-and-shipSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
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 10
Write production-ready code that follows existing patterns and conventions
- Distinctive: line 13
Keep changes focused on what was requested — avoid unrelated improvements
- Distinctive: line 15
If tests fail, fix them before moving on to the next phase of the workflow.
- Distinctive: line 17
When implementation is complete, proceed to the verification and shipping phase.
“Common” is measured: kept by at least 6 in 10 of the 16 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
Implementation
Implement the requested changes:
- Write production-ready code that follows existing patterns and conventions
- Choose verification using
verify-and-ship: use relevant existing tests or direct checks; add new tests only for concrete consequential regressions worth maintaining - Handle edge cases and error scenarios appropriately
- Keep changes focused on what was requested — avoid unrelated improvements
If tests fail, fix them before moving on to the next phase of the workflow.
When implementation is complete, proceed to the verification and shipping phase.
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.

