ship-feature — Claude Code skill: what it does, how to install
ship-feature — a workflow for taking medium or large feature changes from module inspection through implementation, verification, and documentation updates. Covers backend, frontend, and MCP work.
MIT ★ 1,198 updated 2026-10-23
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill ship-feature -a claude-codeWhat ship-feature does
Before editing, the skill asks the agent to inspect affected modules and write a short plan. It then guides implementation of the smallest coherent change, with API and websocket contracts kept stable unless changing them is part of the task.
After implementation, run relevant checks and revise docs when commands, paths, architecture, or behavior have changed. The finish checklist covers tests, build, or typecheck; the scope of changed files; and user-facing docs. A checklist template lives at references/feature-checklist.md.
For medium or large tasks, this gives the work a defined sequence. Broad refactoring is out of scope unless requested, and destructive operations need explicit guardrails. Those constraints matter when a feature request touches existing contracts.
What it helps with
- plan code changes before editing affected modules
- preserve API and websocket contracts while adding functionality
- verify a change with relevant tests, build, or typecheck
- update docs when commands or behavior change
- keep feature work from expanding into unrequested refactors
Example prompts for the agent
- Add a backend feature: inspect the affected modules, draft a plan, implement the change, and run relevant checks.
- Change MCP behavior while keeping API and websocket contracts stable; update docs if the change affects them.
- Review this completed feature task against its checks, changed-file scope, and user-facing documentation.
How to install ship-feature
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill ship-feature -a claude-code2Manually: put the files in place
~/.claude/skills/ship-feature/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ship-feature/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill ship-feature -a codex2Manually: put the files in place
.agents/skills/ship-feature/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill ship-feature -a cursor2Manually: put the files in place
.cursor/skills/ship-feature/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hoangsonww/Claude-Code-Agent-Monitor .claude/skills/ship-feature2Manually: put the files in place
.github/skills/ship-feature/SKILL.md1Skills CLI (Vercel)
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill ship-feature -a gemini-cli2Platform CLI
gemini skills install https://github.com/hoangsonww/Claude-Code-Agent-Monitor --path .claude/skills/ship-featureManually: put the files in place
.devin/skills/ship-feature/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ship-feature
How do I install ship-feature in Claude Code?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill ship-feature -a claude-code. The skill file is at ~/.claude/skills/ship-feature/SKILL.md.
What does ship-feature do?
It guides medium and large feature work through module inspection, planning, implementation, verification, and documentation updates. It also calls for stable API and websocket contracts unless a change is intentional.
Which checks does ship-feature include?
Its finish checklist covers tests, build, or typecheck, the scope of changed files, and user-facing docs. It also includes the template references/feature-checklist.md.
Source text
SKILL.md · MIT
--- name: ship-feature description: 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. --- # 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`
© hoangsonww · MIT · hoangsonww/Claude-Code-Agent-Monitor