Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill ship-feature -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/ship-feature/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ship-feature/

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

Similar skills

All skills for Backend and APIs →

From the same set155

The whole set →
overspend overspend spots the most expensive Claude Code sessions via a local dashboard and displays them in a ranking table. Useful when spending spikes unexpectedly. CX Codex +1 ★ 1,198repo stars top-spenders top-spenders sorts Claude Code sessions by cost and lists the most expensive ones. Use it to inspect session spending and compare the top entries with the total. CX Codex +1 ★ 1,198repo stars runs Pulls recent Workflow-tool fleet runs from the local Agent Monitor and prints a status summary plus a compact table of the latest ones. CX Codex +1 ★ 1,198repo stars recent recent fetches the latest Claude Code sessions from Agent Monitor with costs and run statuses. Useful when you need a quick summary of agent activity and spending. CX Codex +1 ★ 1,198repo stars budget Puts your Claude spend next to a monthly budget you name, then tells you whether you are under it, on pace or already over. CX Codex +1 ★ 1,198repo stars tail-events tail-events fetches recent events from a local Agent Monitor dashboard and displays them in a compact table. Useful for tracking agent tool calls and session state. CX Codex +1 ★ 1,198repo stars mcp-operations The mcp-operations skill guides local MCP server checks, host configuration, and safety settings. Use it when tool connectivity fails or MCP behavior changes. CX Codex +1 ★ 1,198repo stars errors errors pulls recent APIError events from the local Agent Monitor dashboard and prints one line per failure: time, session, short summary. CX Codex +1 ★ 1,198repo stars

Project sponsors

Companies that keep this analytics open