Claude Skill

ship-feature

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.

LLM Mart · 0 points · 11 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download hoangsonww-claude-code-agent-monitor-.claude_skills_ship-feature-83d4df5.zip · 1 KB

hoangsonww/claude-code-agent-monitor 1014 238 forks MIT Updated 1d ago

Part of hoangsonww/claude-code-agent-monitor — 86 skills

Install

skills CLI npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/.claude/skills/ship-feature

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install hoangsonww-claude-code-agent-monitor@llmmart

Git git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole hoangsonww/claude-code-agent-monitor collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Files (claude-code-agent-monitor)

references

feature-checklist.md 717 B

# Feature Checklist

- Scope
  - Problem and success criteria are explicit.
  - Impacted layers identified (server/client/mcp/docs/scripts).

- Implementation
  - Input validation and error handling are explicit.
  - Existing behavior preserved where not in scope.
  - Safety controls preserved.

- Verification
  - Backend: `npm run test:server` when backend changed.
  - Frontend: `npm run test:client` when UI changed.
  - MCP: `npm run mcp:typecheck` + `npm run mcp:build` when MCP changed.

- Documentation
  - `README.md`, `ARCHITECTURE.md`, `SETUP.md`, `INSTALL.md`, `mcp/README.md` updated as needed.
  - Commands in docs match `package.json`.

- Delivery
  - Known risks and unrun checks are clearly stated.

SKILL.md 1 KB

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