agentleFS
Sign inStart free
ivanrvpereiraivanrvpereira/.agents/skills/auto/implement/SKILL.md

implement

Skill19 starsChanged 4 days agoApache-2.0View on GitHub

Implement a piece of work based on a spec or set of tickets.

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

    If the user passes a ticket reference, fetch it from the issue tracker and state its title before starting.

    line 10
  2. Distinctive:

    Before adding or changing tests, read tdd and its linked testing and mocking references.

    line 12
  3. Distinctive:

    Run typechecking regularly, single test files regularly, and the full test suite once at the end.

    line 14
  4. Distinctive:

    Commit your work to the current branch.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 170 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 the work described by the user in the spec or tickets.

If a parent agent delegated this work to you, its brief replaces the user's request: take the work from the brief instead of fetching tickets, ask the parent wherever this skill says to ask the user, and skip the final review and commit steps because the parent owns them.

If the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.

Before adding or changing tests, read tdd and its linked testing and mocking references. Apply its loop at the seams already approved in the spec or project guidance. If the seams are missing or need to change, confirm them with the user before writing tests.

Run typechecking regularly, single test files regularly, and the full test suite once at the end.

Once done, call the Skill tool with "code-review" to review the work.

Commit your work to the current branch.

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.

Check your setup, free