agentleFS
Sign inStart free
karloowskarloows/orchraft/skills/forgehand/SKILL.md

forgehand

Skill1 starsChanged 51 days agoApache-2.0View on GitHub

Have the AI implement a requested code change and run focused validation without committing, pushing, or changing GitHub. Use when the user asks to fix, build, refactor, or test code.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for implementation work that should stay in the working tree.

    line 8
  2. Distinctive:

    Read the repository's instructions, relevant policies, and existing code before editing.

    line 12
  3. Distinctive:

    Run the narrowest useful validation after editing.

    line 16
  4. Distinctive:

    Stop before committing, pushing, creating or updating branches, opening or updating pull requests, posting reviews, changing issues, …

    line 17
  5. Very specific:

    If the work needs a plan first, stop and direct the user to warplan.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Forgehand Workflow

Use this skill for implementation work that should stay in the working tree.

Rules

  • Read the repository's instructions, relevant policies, and existing code before editing.
  • Trace the real flow and reuse existing helpers and patterns.
  • Make the smallest correct change and preserve unrelated work.
  • Run the narrowest useful validation after editing.
  • Stop before committing, pushing, creating or updating branches, opening or updating pull requests, posting reviews, changing issues, publishing releases, or merging.
  • Report the files changed and validation results honestly.

If the work needs a plan first, stop and direct the user to warplan. If the user wants the completed work shipped, stop and direct them to ship.

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