agentleFS
ApicurioApicurio/apicurio-registry/.claude/skills/implement-change/SKILL.md

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

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.
  • yaohuangguanSkill

    audit-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

  • yaohuangguanSkill

    change-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

  • SauravSrivastavSkill

    debug-failure

    Diagnose a failing test, command, or runtime behavior using evidence and produce a minimal verified fix.

    Also in 3 projects that use this

  • MicrosoftSkill

    fix-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

  • srclightSkill

    refactor-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

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
  1. Very specific:

    Read AGENT-VERIFICATION.md at the repository root.

    line 8
  2. Distinctive:

    Check concrete outcomes, including resulting state and failure cases where relevant.

    line 16
  3. Very specific:

    If further analysis is warranted, recommend /verify-change, explicitly requesting a challenge when blind-spot investigation is needed.

    line 27

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

  1. 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.
  2. 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.
  3. Check concrete outcomes, including resulting state and failure cases where relevant. Use existing tests as a baseline and add meaningful coverage as required.
  4. 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.
  5. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.