Ship Feature
This is a structured workflow for implementing features across your stack without breaking things. It enforces the basics that often get skipped: exploring what you're about to touch, writing down a plan before coding, running tests, and updating docs when behavior changes. The checklist keeps you honest about API stability and making sure destructive operations stay behind guardrails. It's useful when you need to ship something that spans multiple parts of the codebase and want to avoid the usual "it worked on my machine" surprises. The discipline is the point here, especially the part about keeping diffs scoped and intentional.
- GitHub stars
- 455
- last updated
- Jun 11, 2026
Install
$ npx -y skills add hoangsonww/claude-code-agent-monitor --skill ship-feature --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
Sponsors
Details
- Repository
- github.com/hoangsonww/claude-code-agent-monitor
- Categories
- Frontend Development, Backend & APIs, DevOps & CI/CD, Documentation, AI & Agent Building, Release Management
- License
- MIT
- First seen
- Jun 11, 2026
