メニュー
Open a spec's PR correctly: the right branch, a conventional-commit title, a body that maps the diff to the spec's acceptance checks with a test plan, and the spec file included in the diff. Use when a change is ready to push for review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
SDLC orchestration plugin for Claude Code. Drives projects through a 9-phase software development lifecycle with company-configurable profiles, compliance gates, and quality enforcement. Triggers: "start sdlc", "sdlc setup", "initialize project lifecycle", "run phase gate", "advance phase", "sdlc status", "compliance check", "project setup wizard", "lifecycle management".
Add a new endpoint / route / use case / service the way this Node + TypeScript codebase already does it. Use when building an API surface, a request handler, a validator, a port/adapter, or a container registration in a Node/TypeScript repo. Finds the one canonical example and mirrors its layering, validation, error model, and test shape — so agents extend the codebase instead of inventing a second way to do something it already does. The Node realization of the core api-pattern skill.
Add a new module / CLI command / service function / loader the way this Python codebase already does it. Use when building a public surface, a command entry point, a data loader, a validator, or a new package module in a Python / uv repo. Finds the one canonical example and mirrors its layering, typing, error model, and test shape — so agents extend the codebase instead of inventing a second way to do something it already does. The Python realization of the core api-pattern skill.
Build a golden set for an agentic (LLM-powered) spec — the acceptance criteria for probabilistic behavior. Use when a spec's deliverable is an agent/prompt/tool and needs evals before build, or when adding cases from a production failure. Produces a versioned golden-set.yaml under eval-datasets/specs/<feature>/, referencing the spec file.
Add a new endpoint / MediatR command or query / handler / service the way this .NET codebase already does it. Use when building an API surface, a CQRS handler, a controller, a validator, or a DI registration in a .NET / Clean Architecture repo. Finds the one canonical example and mirrors its layering, validation, error model, and test shape — so agents extend the codebase instead of inventing a second way to do something it already does. The .NET realization of the core api-pattern skill.
Add a new endpoint / handler / service the way this codebase already does it. Use when building an API surface, a CQRS handler, a controller, or a service registration. Finds the one canonical example and follows it exactly — so agents reuse the established pattern instead of inventing a new one each run.
| name | pr-writer |
| description | Open a spec's PR correctly: the right branch, a conventional-commit title, a body that maps the diff to the spec's acceptance checks with a test plan, and the spec file included in the diff. Use when a change is ready to push for review. |
| allowed-tools | ["Read","Grep","Glob","Bash"] |
A PR is where intent and implementation are reviewed together, so it must carry both. This skill produces the PR the merge bar and the grader expect.
spec/NNNN-name), never to the default branch.review-gate hook blocks the push until /code-review and /simplify have run for HEAD —
run those first (see the kit's built-in dependencies).spec/NNNN-name (create it from the default branch if not).git add -A). Title is a conventional commit —
type: description, imperative, lowercase, under 72 chars (feat:, fix:, refactor:,
docs:, test:, chore:, perf:, ci:). Every agent commit is co-authored for provenance.specs/NNNN-name.md must be part of the PR so the
reviewer and grader see intent + implementation in one view.dotnet test etc.), not "should pass."risk:high label if HIGH.gh pr create) with that title and body. Do not approve or merge it — a
non-author owns the verdict.