agentleFS
Sign inStart free
philoserfphiloserf/claude-code-config/skills/implement/SKILL.md

implement

Skill14 starsChanged 8 days agoMITView on GitHub

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

191 other projects use a version of this, 68 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, ask-matt and 7 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.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • GoogleSkill

    ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 91 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 50 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 88 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 42 projects that use this

  • GoogleSkill

    resolving-merge-conflicts

    Use when you need to resolve an in-progress git merge/rebase conflict.

    Also in 83 projects that use this

  • +1 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never commit to main. Unless you're already on a feature branch, start one with ~/.claude/bin/pr-cycle start <branch>.

    line 11
  2. Distinctive:

    Call the Skill tool with "tdd" where possible, at pre-agreed seams.

    line 13
  3. Distinctive:

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

    line 15
  4. Very specific:

    Commit your work to the branch.

    line 17
  5. Very specific:

    Stop there. Shipping is the user's call: report the branch, and draft the PR body with the pr skill (Closes #<n> for each ticket) so …

    line 19

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

Issue-tracker operations and labels are in ~/.claude/references/github-tracker.md. If the user passes a ticket reference, fetch it and state its title before starting. If the reference is ambiguous, ask.

Never commit to main. Unless you're already on a feature branch, start one with ~/.claude/bin/pr-cycle start <branch>.

Call the Skill tool with "tdd" where possible, at pre-agreed seams.

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

Commit your work to the branch. Then call the Skill tool with "spec-review" to review it, commit the fixes for what it finds, and record the review with ~/.claude/bin/pr-cycle reviewed <branch>.

Stop there. Shipping is the user's call: report the branch, and draft the PR body with the pr skill (Closes #<n> for each ticket) so pr-cycle ship is one command away.

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