agentleFS
ApurvBazariApurvBazari/claude-plugins/.claude/skills/feature-done/SKILL.md

feature-done

Skill3 starsChanged 48 days agoMITView on GitHub

Run pre-completion checklist after finishing a plugin feature — validates, checks docs, suggests commit

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. dip497/hivemind★ 17same name
    2. midFang/ai-agent-skills-workflow★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this before considering a plugin feature complete.

    line 8
  2. Distinctive:

    If only WARNs are present, note them and continue.

    line 14
  3. Distinctive:

    README.md: If user-facing behavior changed (new skill, new command, changed arguments), verify README is updated

    line 20
  4. Distinctive:

    Plugin CLAUDE.md: If internal conventions changed (new patterns, new architecture), verify the subdirectory CLAUDE.md is updated

    line 21
  5. Distinctive:

    CHANGELOG.md: Verify there's an entry for this change

    line 22
  6. Distinctive:

    If plugin code changed (not just docs):

    line 28
  7. Very specific:

    Check if plugin.json version was bumped

    line 29
  8. Very specific:

    Check if marketplace.json version was updated to match

    line 30
  9. Distinctive:

    If not bumped, suggest a version bump (patch for fixes, minor for features)

    line 31
  10. Distinctive:

    Run git status and review:

    line 35
  11. Distinctive:

    Always run /validate first — it's the foundation

    line 56
  12. Distinctive:

    Don't auto-commit — suggest and let the user decide

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

/feature-done — Feature Completion Checklist

Run this before considering a plugin feature complete. Validates the plugin, checks documentation, and suggests a commit.

Step 1: Run Validation

Invoke the /validate skill to run all quality checks. If any check returns FAIL, stop and report the failures — they must be fixed before proceeding.

If only WARNs are present, note them and continue.

Step 2: Check Documentation

Review the git diff to identify what changed. For each modified plugin:

  1. README.md: If user-facing behavior changed (new skill, new command, changed arguments), verify README is updated
  2. Plugin CLAUDE.md: If internal conventions changed (new patterns, new architecture), verify the subdirectory CLAUDE.md is updated
  3. CHANGELOG.md: Verify there's an entry for this change

Report any missing documentation updates as items to address.

Step 3: Version Check

If plugin code changed (not just docs):

  • Check if plugin.json version was bumped
  • Check if marketplace.json version was updated to match
  • If not bumped, suggest a version bump (patch for fixes, minor for features)

Step 4: Git Status Review

Run git status and review:

  • Are there untracked files that should be committed?
  • Are there files that should NOT be committed (temporary files, local configs)?
  • Is the working tree clean enough for a commit?

Step 5: Suggest Commit

Based on the changes, suggest a conventional commit message:

type(scope): description

- type: feat, fix, refactor, docs, chore
- scope: plugin name (onboard, notify, handoff) or repo-level
- description: concise "why" in imperative mood

Present the suggested message and ask if the user wants to commit.

Key Rules

  • Always run /validate first — it's the foundation
  • Don't auto-commit — suggest and let the user decide
  • Version bumps are mandatory for code changes, optional for doc-only changes
  • One logical change per commit — if multiple plugins changed independently, suggest separate commits

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.