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
- dip497/hivemindtheir own version, first seen Nov 1, 2026
- midFang/ai-agent-skills-workflowtheir own version, first seen Jun 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- dip497/hivemind★ 17same name
- 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.
- CLAUDE.mdCLAUDE.md
- doc-auditSkill
- progressive-disclosureSkill
- release-docsSkill
- test-plugins-locallySkill
- validateSkill
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
- Distinctive: line 8
Run this before considering a plugin feature complete.
- Distinctive: line 14
If only WARNs are present, note them and continue.
- Distinctive: line 20
README.md: If user-facing behavior changed (new skill, new command, changed arguments), verify README is updated
- Distinctive: line 21
Plugin CLAUDE.md: If internal conventions changed (new patterns, new architecture), verify the subdirectory CLAUDE.md is updated
- Distinctive: line 22
CHANGELOG.md: Verify there's an entry for this change
- Distinctive: line 28
If plugin code changed (not just docs):
- Very specific: line 29
Check if plugin.json version was bumped
- Very specific: line 30
Check if marketplace.json version was updated to match
- Distinctive: line 31
If not bumped, suggest a version bump (patch for fixes, minor for features)
- Distinctive: line 35
Run git status and review:
- Distinctive: line 56
Always run /validate first — it's the foundation
- Distinctive: line 57
Don't auto-commit — suggest and let the user decide
≈ “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.
Files
/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:
- README.md: If user-facing behavior changed (new skill, new command, changed arguments), verify README is updated
- Plugin CLAUDE.md: If internal conventions changed (new patterns, new architecture), verify the subdirectory CLAUDE.md is updated
- 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.jsonversion was bumped - Check if
marketplace.jsonversion 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 moodPresent 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
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
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.

