Skip to content
Skills Library
Programming · Building & coding

implement-change

/implement-change

Plan, make and check a code change from start to finish. Use this for any feature, bug fix, enhancement or behaviour change, including requests that sound small such as "add a field", "fix this" or "make it support X". It keeps the change small, complete and verified.

Licence
MIT
Last repository change
07.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Plan, make and check a code change from start to finish. Use this for any feature, bug fix, enhancement or behaviour change, including requests that sound small such as "add a field", "fix this" or "make it support X". It keeps the change small, complete and verified.

Triggers from the description

add a fieldfix thismake it support X
Original author description

Plan, make and check a code change from start to finish. Use this for any feature, bug fix, enhancement or behaviour change, including requests that sound small such as "add a field", "fix this" or "make it support X". It keeps the change small, complete and verified.

How it works

  1. When to use
  2. Steps
  3. Stop and ask when
  4. Common mistakes
  5. Example
  6. Report
Original SKILL.md headings · 93 lines, 600 words
SKILL.md preview
---
name: implement-change
description: Plan, make and check a code change from start to finish. Use this for any feature, bug fix, enhancement or behaviour change, including requests that sound small such as "add a field", "fix this" or "make it support X". It keeps the change small, complete and verified.
---

# Implement a change

A good change is complete and small. It updates every place that needs it and
touches nothing else. The common failures are missing a related place, doing
extra work, and stopping before anything was checked.

## When to use

Any task that changes behaviour. For structure-only work use `refactor-safely`.
For a failure with an unknown cause, start with `debug-failure`.

## Steps

1. **Restate the task.** Write one sentence on the goal and a short list of what
   must be true when it is done. If two readings would produce different code,
   ask before you start.

2. **Orient.** If you have not read this area, follow `orient-in-codebase`.

3. **Find every affected place.** Search for the names you will change. Check
   callers, tests, docs, translations, schemas, config, and lists that repeat a
   value such as routes, plans or permissions. A missed copy is the most common
   cause of a half-finished change.

4. **Choose the smallest design.** Reuse existing helpers and patterns. Do not
   add options, abstractions or dependencies the task did not ask for. Write the
   plan as a short list of files and what changes in each. Place new files by
   `structure-code`.

5. **Open the matching skill.** Use `secure-change` for permissions, input or
   secrets, `change-data-safely` for stored data, and `use-external-api` for a
   third-party call.

6. **Write a test first where practical.** Make it fail for the expected reason
   before you change the code. Follow `write-tests`.

7. **Make one small edit at a time.** Run the nearest test after each step. If it
   breaks, you know which edit caused it.

8. **Handle the unhappy paths.** For each new input or dependency, decide what
   happens when it is empty, invalid, slow, unauthorized or failing.

9. **Review your own diff.** Run `git diff` and read every line:

   - Is each line needed for this task?
   - Did you leave debug output, commented code or unused imports?
   - Did you change formatting in unrelated lines?
   - Are existing users and existing data still fine?

10. **Finish.** Follow `verify-and-report`.

## Stop and ask when

- The requirement is ambiguous and the choice affects behaviour.
- The change needs a new dependency, a public API change or a data migration
  that the task did not mention.
- You have failed three times with the same approach.

## Common mistakes

| Tempting move | Why it fails | Do this instead |
| --- | --- | --- |
| Rewrite the whole file | Hides real changes and adds risk | Make targeted edits |
| Fix nearby issues too | Makes review harder and adds risk | Mention them in your report |
| Add a config option "just in case" | Adds code nobody needs | Build what was asked |
| Stop at the happy path | Most incidents are in failure paths | Handle each failure in step 8 |
| Say it should work | Nothing was tested | Run it and report the result |

## Example

Task: "Add a `nickname` field to user profiles."

Weak plan: "Add `nickname` to the User model."

Strong plan:

```markdown
Done when: users can save, see and clear a nickname of at most 40 characters.
Files:
- migrations/: add a nullable column
- models/user: add the field
- api/profile: accept, validate and return it; reject over 40 characters
- ui/profile: add the input and error message
- locales/: add the label in each language
- tests: both sides of the limit, blank value, another user's profile
Unchanged: existing users keep a null nickname.
```

## Report

Use the template in `verify-and-report`.

Versions

RepositoryScoreLicence
This page · yaohuangguan/agent-playbook100MIT
shivaedev/pardes90MIT
Jed-Tech/spar-kit85Apache-2.0
codagent-ai/agent-skills84MIT

Database snapshot: 13.11.2026 · package version e0de96028f55 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100implement
    Implement a feature, bug fix, or code change in MegaLinter. Use whenever the user asks to add a feature, fix a bug, or make a code change - with or without a prior /design phase.
  • 100implement
    Make the code change a ticket or bug report asks for, then prove it with the repo''s own checks. Use when: told to fix, change or build something, such as "fix this bug".
  • 90task
    Make a small change to a shipped product — a bug fix, behavior tweak, micro-feature, refactor, or perf fix — as one verified slice, syncing the affected feature spec on the way out. Use for day-to-day requests like "fix X", "change Y to do Z", or a single small feature that…
  • 100brief
    Brief a small change, then implement, review and verify it, with no plan file. Use when someone asks for "a quick fix", "a small change", "can you tweak", "change this text", "fix this bug", "add a button", "update the docs", one clear thing with one obvious approach; also the…
  • 85ultrawork
    Makes one code change — a feature, a bug fix, a refactor — with evidence at every step — reads the code before touching it, reproduces or pins down the behaviour, makes the smallest change that solves it, proves the result with commands run in this session, and stops when it is…
  • 100change-implementation
    Implement an issue, feature, or non-trivial bug fix in an existing codebase as one complete change, from the request and its discussion through code, tests, and documentation, including breaking changes when the repository allows them. Use when asked to implement, fix, or build…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.