agentleFS
MrZarrarMrZarrar/Jarvis-Sub-Agent-Dashboard/.claude/skills/ship-feature/SKILL.md

ship-feature

Skill0 starsChanged 4 months agoMITView on GitHub

Implement a feature safely end-to-end in this repository. Use when adding or changing functionality across backend, frontend, or MCP with required verification and documentation updates.

16 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

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 7

    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:

    Use this workflow for medium or large implementation tasks.

    line 8
  2. Distinctive:

    Write a short implementation plan before editing.

    line 12
  3. Distinctive:

    Run relevant verification commands.

    line 14
  4. Distinctive:

    Update docs when commands, paths, architecture, or behavior changed.

    line 15
  5. Distinctive:

    Keep API and websocket contracts stable unless intentionally changed.

    line 18
  6. Distinctive:

    Keep destructive operations behind explicit guardrails.

    line 19
  7. Distinctive:

    Avoid broad refactors in feature tickets unless requested.

    line 20

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

Ship Feature

Use this workflow for medium or large implementation tasks.

Steps

  • Explore impacted modules first.
  • Write a short implementation plan before editing.
  • Implement smallest coherent diff that satisfies requirements.
  • Run relevant verification commands.
  • Update docs when commands, paths, architecture, or behavior changed.

Required quality checks

  • Keep API and websocket contracts stable unless intentionally changed.
  • Keep destructive operations behind explicit guardrails.
  • Avoid broad refactors in feature tickets unless requested.

Finish checklist

  • Tests/build/typecheck completed or explicitly reported as not run.
  • Changed file set is scoped and intentional.
  • User-facing docs updated if behavior changed.

References

  • Checklist template: references/feature-checklist.md

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.