ship-feature

Featured

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.

Web & Frontend 989 stars 233 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%

100

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# 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`

Details

Author: hoangsonww
Repository: hoangsonww/Claude-Code-Agent-Monitor
Created: 6 months ago
Last Updated: 2 days ago
Language: TypeScript
License: MIT

Integrates with

SQLite · Database Tailwind CSS · Frontend Express.js · Backend WebSocket · API

Bundled in these plugins

Claude-Code-Agent-Monitor

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

ship-feature-e2e

Use when the user runs /ship-feature-e2e, pastes an existing GitHub issue (#N / URL), or says "ship this feature end to end", "implement this issue fully", "feature to main", "issue to PR to merge", "act then merge reinstall" — one feature or one issue through issue → worktree/branch → implement → unit + e2e happy paths → PR with summary + confidence 1–10 → local act → merge → reinstall. Orchestrate by loading and reusing sdlc-tasks-executions, organized-commits, finish-and-ship (and siblings); do not reimplement those skills. Prefer over finish-and-ship when merge/act/reinstall are in scope; over messy-repo-orchestrator for a single feature/issue.

0 Updated 3 weeks ago

YosefHayim

Web & Frontend Listed

implement-feature

Implement an approved software feature as thin end-to-end slices before hardening individual components. Use when a concrete feature design or implementation plan already exists and the task requires safe incremental implementation in an existing codebase.

0 Updated 2 weeks ago

qduc

Code & Development Listed

ship-it

Implement a scoped change and commit it locally. Use when the user wants a feature, fix, or planned phase delivered as a commit — not a PR; use ship-pr for that.

0 Updated 4 days ago

MichaelHolley