菜单
Post-implementation completion workflow. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers when implementation is done, when the user says "finish", "done", "complete", or after implementation tasks are finished.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate and validate conventional commit messages following the conventionalcommits.org spec. Use whenever the user wants to commit code, mentions commit messages, git commit, or asks to create a commit. Triggers on "commit", "git commit", "conventional", or when reviewing commit message format.
Compact the current conversation into a handoff document for another agent to pick up.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Grill the user relentlessly about a plan, decision, or idea, maintaining the project's domain model (CONTEXT.md, ADRs) as decisions crystallise. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Conversational design workshop for new features. Interviews the human one question at a time, explores 2-3 approaches with trade-offs, and presents the design section by section for approval before writing the spec. Combines requirements discovery with codebase research and architecture design. Use when the user says "create a spec", "design this feature", "let's brainstorm", "what should we build", or at the start of any feature/refactor/complex-bug workflow.
Skill routing and workflow orchestration. Routes to correct spec skill based on task type. Establishes discipline and manages transitions between workflow phases. Use when starting any conversation or task to determine which spec skill applies.
| name | spec-finish |
| description | Post-implementation completion workflow. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers when implementation is done, when the user says "finish", "done", "complete", or after implementation tasks are finished. |
| user-invocable | true |
Post-implementation workflow: validate → review → stack commits → prepare PR.
Before starting, verify:
If not complete → go back to spec-implement.
Run validation checks.
npm test
# or
pytest
# or
cargo test
npm run typecheck
# or
python -m mypy
# or
cargo check
npm run lint
# or
ruff check .
# or
cargo clippy
npm run build
# or
go build ./...
If any fail: Return to spec-implement to fix.
If all pass: Proceed.
Use the Skill tool to invoke code-review skill for comprehensive code review.
git log --onelinegit rebase -i <base-branch>Steps 1-4 (validate, review, stack commits, update docs) must all be complete before proceeding. If code-review found blocking issues, stop — return to spec-implement to fix them. Do not proceed to Step 5b.
Before creating the PR, present a summary to the human:
## Completion Summary
**Feature:** [name]
**Tests:** [passed/failed]
**Type Check:** [passed/failed]
**Lint:** [passed/failed]
**Review:** [passed/issues found]
**Commits:** [N commits in stack]
**Ready for PR:** [yes/no]
Only when the summary shows Ready for PR: yes, invoke the
code-pull-request skill to create the PR. It
detects the platform (GitHub/GitLab), checks for an existing PR, finds a
template, generates the body from commits, and opens the PR via gh or glab.
"Implementation complete. [N] commits stacked. Opening PR now."
This skill orchestrates other skills: