메뉴
Run pm-cli release-readiness workflows — validation, coverage gates, changelog, GitHub checks — using native MCP tools with linked evidence. Use when preparing releases, publishing, or verifying post-release state.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Plan and organize pm CLI work — triage requests, break epics into tasks, prioritize the backlog, and keep the tracker clean. Use when decomposing features, planning sprints, or organizing incoming requests.
Use pm-cli natively in Codex through bundled MCP tools for planning, tracking, mutation, validation, and reporting without invoking the pm shell command.
Audit pm-cli repositories with native pm MCP tools — health checks, validation, duplicate detection, aggregation, privacy review, and workflow health. Use when performing broad repository audits, release readiness checks, or agent-workflow health reviews.
Run the pm-cli developer execution loop — orient, claim, implement, link evidence, verify, and close — with native MCP tools. Use when coding, debugging, refactoring, or shipping changes tracked in pm items.
Use pm CLI natively in Claude Code through MCP tools for planning, tracking, mutation, validation, and reporting. Use this skill whenever work should be tracked through pm — before implementing, during implementation, and at close.
Audit pm-cli repositories with native pm MCP tools, preserving duplicate checks, privacy boundaries, linked evidence, and verification records.
| name | pm-release |
| description | Run pm-cli release-readiness workflows — validation, coverage gates, changelog, GitHub checks — using native MCP tools with linked evidence. Use when preparing releases, publishing, or verifying post-release state. |
Use for release preparation, publication, and post-release verification.
pm_search).TaskCreate to show the release in Claude Code's task panel.pnpm build — clean buildnode scripts/run-tests.mjs coverage — full coverage gatepm_validate with all checkspm_health for tracker statusgh run list --limit 5 after push.pm_comments.TaskUpdate(completed).TaskCreate:
subject: "[pm-xxxx] Release: <version>"
description: "Release gate tracking for pm-xxxx"
activeForm: "Running release gates"
Save the taskId. Then TaskUpdate(in_progress).
TaskUpdate: { taskId: <saved>, status: "completed" }
{ "tool": "pm_validate", "args": { "options": { "checkResolution": true, "checkHistoryDrift": true, "checkFiles": true } } }
{ "tool": "pm_health", "args": {} }
{ "tool": "pm_context", "args": { "options": { "depth": "standard" } } }
{ "tool": "pm_docs", "args": { "id": "pm-xxxx", "author": "claude-code-agent", "options": { "add": ["path=CHANGELOG.md,scope=project,note=release-notes"] } } }
{ "tool": "pm_files", "args": { "id": "pm-xxxx", "author": "claude-code-agent", "options": { "add": ["path=package.json,scope=project,note=version"] } } }
{
"tool": "pm_comments",
"args": {
"id": "pm-xxxx",
"author": "claude-code-agent",
"options": {
"add": "Release evidence: build ok. Tests pass. 100% coverage. pm validate ok. GitHub CI green. npm publish ok."
}
}
}
pnpm build # TypeScript build
node scripts/run-tests.mjs coverage # Full test + coverage
node scripts/release/run-gates.mjs # All release gates
gh run list --limit 5 # GitHub CI status
gh run view <run-id> # Detailed run status
path for real repository tracking — only for sandbox tests.npm publish or version tag.