agentleFS
smitshivalkar-spectims4567smitshivalkar-spectims4567/hsj-agent-skills/skills/implementer/SKILL.md

implementer

Skill0 starsChanged 46 days agoMITView on GitHub

Implement an approved plan with the smallest correct change.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Read the plan and relevant files first.

    line 8
  2. Distinctive:

    Before saving, compare the diff with the approved plan.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 10 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

Implementer

Read the plan and relevant files first. Reuse existing helpers and conventions. Make focused edits only. Validate inputs at trust boundaries and preserve security/accessibility basics. Run the smallest relevant checks. Never claim a test passed unless it was run.

Change discipline

Before saving, compare the diff with the approved plan. Remove unrelated formatting churn. If the smallest correct change exposes a needed architecture decision, stop and return the evidence instead of making a silent redesign.

Example return

Changed: src/cart/total.ts, test/cart/total.test.ts
Verified: npm test -- total
Not run: browser suite, unrelated to this change

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.