ship-feature
The ship-feature skill provides a structured workflow for implementing medium to large features across a Claude Code repository, encompassing backend, frontend, and MCP components. Use it when adding or modifying functionality that requires exploration of affected modules, implementation planning, verification testing, and documentation updates, with built-in safeguards for API stability, destructive operations, and quality assurance checkpoints.
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor /tmp/ship-feature && cp -r /tmp/ship-feature/.claude/skills/ship-feature ~/.claude/skills/ship-featureSKILL.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`
Operate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.
Review backend route and hook logic for regressions, data integrity risks, and missing tests.
Review React UI changes for behavior regressions, state consistency, and UX breakage.
Review MCP server changes for tool safety, schema quality, and host integration correctness.
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.