agentleFS
caterpi11arcaterpi11ar/giclaw/.agents/skills/implement/SKILL.md

implement

Skill9 starsChanged 29 days agoNo licenceView on GitHub

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

218 other projects use a version of this, 56 of them edited; 55 of 56 edited versions we compared changed its rules; 5 new projects in the last 4 weeks, against 6 the 4 before.

How people change it

55 of 56 edited versions changed its rules, and some changes recur.

Of the 56 edited versions we compared: 1 keep every rule, 55 made changes of their own.

Rules people drop

  1. 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.dropped by 51 of 55
  2. Call the Skill tool with "tdd" where possible, at pre-agreed seams.dropped by 51 of 55
  3. Commit your work to the current branch.dropped by 5 of 55
  4. Run typechecking regularly, single test files regularly, and the full test suite once at the end.dropped by 4 of 55

Rules people add

  1. Use /tdd where possible, at pre-agreed seams.added by 44 of 55

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 5 new projects took it in the last 4 weeks, 0.8× the 4 weeks before.thin data

Week of Sep 20: 1 new projectWeek of Sep 27: 1 new projectWeek of Oct 4: 2 new projectsWeek of Oct 11: 2 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 2 new projectsWeek of Nov 1: 2 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 11 in all, so this is a hint, not a trend.

Most recently taken up by

The file

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.