ship-feature
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.
pinned to #8f87ce1updated 2 weeks ago
Ask your AI client: “install skills/ship-feature”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/ship-featuremetahub onboarded this repo on the author's behalf.
If you own github.com/hoangsonww/Claude-Code-Agent-Monitor on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
789
Last commit
2 weeks ago
Latest release
published
- #ai-agents
- #claude-agents
- #claude-code
- #claude-skills
- #express
- #expressjs
- #macos-app
- #node
- #nodejs
- #python
- #react
- #rest-api
- #rfc-6455
- #sqlite
- #sqlite3
- #tailwind
- #tailwindcss
- #typescript
- #vite
- #websocket
About this skill
Pulled from SKILL.md at publish time.
Use this workflow for medium or large implementation tasks.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.8f87ce1· 2 weeks ago
Kind-specific
22Skill: SKILL.md present
found at .claude/skills/ship-feature/SKILL.md · frontmatter source: SKILL.md
Skill: body content presentwarn
Body is short (113 words · 818 chars) — Claude has little to go on
Add concrete usage steps, example invocations, and any reference links. (≥3 code blocks lifts a short body to pass.)
Skill: triggers declaredwarn
No `trigger` phrases in SKILL.md frontmatter
Add `trigger:` lines so Claude knows when to activate this skill — e.g. `when building MCP servers` or `for diagram creation`.
Skill: allowed-tools scope
no allowed-tools restriction (Claude may use anything)
Release history
1- releasecurrent8f87ce1warn2 weeks ago
Contents
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
Reviews
No reviews yet. Be the first.
Related
Browser Use
🌐 Make websites accessible for AI agents. Automate tasks online with ease.
orchestration-patterns
>
migration-patterns
>
mh install skills/ship-feature