implement-change
Skill951 starsChanged 13 days agoApache-2.0View on GitHub
Implement approved behavioral criteria and produce executed verification evidence. Use when the user asks to execute an agreed plan or invokes /implement-changes.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- CsHeng/agent-skillstheir own version, first seen Nov 9, 2026
- 0xdeafcafe/skillstheir own version, first seen Nov 6, 2026
- yaohuangguan/remote-arctheir own version, first seen Nov 1, 2026
- Remote-Arc/remote-arctheir own version, first seen Nov 1, 2026
- Codagent-AI/agent-skillstheir own version, first seen Nov 1, 2026
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
Used with
Projects with it also use audit-test-suite, change-data-safely and 9 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.
yaohuangguanSkillaudit-test-suite
Find where an existing test suite is weak and decide what to test next, ranked by risk. Use this when asked to add missing tests, find gaps, raise coverage, assess test quality or see which areas are thin, even if the request only mentions a coverage percentage.
Also in 3 projects that use this
yaohuangguanSkillchange-data-safely
Change a database schema or stored data without breaking running code or losing data. Use this for any migration, new or changed column, backfill, bulk update, delete, index, or change to a stored format, including in small projects. Data mistakes are often impossible to undo.
Also in 3 projects that use this
SauravSrivastavSkilldebug-failure
Diagnose a failing test, command, or runtime behavior using evidence and produce a minimal verified fix.
Also in 3 projects that use this
MicrosoftSkillfix-flaky-test
Reproduces and fixes flaky or quarantined tests. Tries local reproduction first (fast), then falls back to CI reproduce workflow (reproduce-flaky-tests.yml). Use this when asked to investigate, reproduce, debug, or fix a flaky test, a quarantined test, or an intermittently failing test.
Also in 3 projects that use this
srclightSkillrefactor-safely
This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.
Also in 5 projects that use this
- +6 more from yaohuangguan
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- pnpm/pnpm★ 37ksame name
- verdaccio/verdaccio★ 18ksame name
- Codagent-AI/agent-skills★ 31same name
- manhds82/claude-code-anyllm★ 16same name
- taljeon/plzdo★ 9same name
- yaohuangguan/remote-arc★ 5same name
- CsHeng/agent-skills★ 3same name
- otaviobarros/agent-engineering★ 3same name
- EJRyan89/coding-agent-skills★ 2same name
- SaKaNa-Y/skills★ 2same 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 repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- apicurio-test-qualitySkill
- challenge-changeSkill
- plan-changeSkill
- sdk-updateSkill
- security-reviewSkill
- storage-variant-guideSkill
- verify-changeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
1
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
- Very specific: line 8
Read AGENT-VERIFICATION.md at the repository root.
- Distinctive: line 16
Check concrete outcomes, including resulting state and failure cases where relevant.
- Very specific: line 27
If further analysis is warranted, recommend /verify-change, explicitly requesting a challenge when blind-spot investigation is needed.
“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
Implement a Change
Read AGENT-VERIFICATION.md at the repository root. Follow its shared workflow
contract and section 3. This skill may edit the scoped implementation and tests.
- Reuse approved criteria, plan, review level, and the user's edge case. If criteria
are missing, load
plan-change(or read its skill file) and stop for agreement. - Inspect status and preserve unrelated work. Implement the smallest change that satisfies the agreed criteria, following repository conventions and relevant specialist skills from the shared contract.
- Check concrete outcomes, including resulting state and failure cases where relevant. Use existing tests as a baseline and add meaningful coverage as required.
- Execute relevant supported checks from
DEVELOPING.md. For a fix, demonstrate expected regression failure before and success after without disturbing the user's working tree. Report blockers rather than substituting setup failures for evidence. - Provide a public-interface reproduction for behavior changes, with setup, expected results, and cleanup. Mark it executed or unexecuted. Run required test-quality review when tests change. Reassess review depth if the scope grows.
Return the shared evidence summary and remaining human decision. Do not rerun
successful checks without a reason. Do not commit or push unless explicitly requested.
If further analysis is warranted, recommend /verify-change, explicitly requesting
a challenge when blind-spot investigation is needed;
do not silently broaden the implementation beyond the agreed task.
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.

