菜单
Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Explore the codebase and write a discovery brief. Use when discovering scope, surveying a codebase, or starting a feature.
QA passed — merge branch to main, move ticket to Done, delete branch. Use after QA sign-off on a completed feature.
Run one fully-autonomous development iteration. Picks a ticket (from --focus or backlog via ideator), then runs the `orchestrator autopilot <slug>` workflow subcommand. This skill should be used when the user says 'autopilot', 'autonomous', 'self-improve'.
Create commits in logical groups. This skill should be used when the user says 'commit-group', 'group commits', 'organize commits', or when there are multiple unstaged changes that should be organized into atomic commits.
Fetch curated, agent-optimized library documentation via Context Hub (chub). Use when implementing features that use external libraries, when Context7 returns noisy/incomplete docs, when you need language-specific or version-specific API docs, or when the user says "chub", "context hub", "get docs for X". Prefer this over Context7 for libraries in chub's registry — curated docs have less noise and better code examples.
Review design.md and tasks.yaml for completeness and quality. Use when reviewing a design before implementation.
| name | complete-feature |
| description | Complete feature — verify, signoff, archive. Runs only the complete phase of the orchestrate workflow. This skill should be used when the user says 'complete feature', 'finish feature', 'merge to main'. |
| user-invocable | true |
| args | [{"name":"feature-id","description":"Feature ID (e.g., HL-170). Auto-detected from worktree/branch if omitted.","required":false}] |
orchestrator complete <change-id>
This is the complete workflow subcommand (config/workflows/complete.yaml), routed like any other workflow via orchestrator-run.sh --schema complete (not a separate driver).
On success: archive on the feature branch (complete phase), then merge to the default branch (unconditional — invoking orchestrator complete IS the deliberate merge signal), then remove the worktree. If merge fails, the worktree is kept.