菜单
Use when the user says "implement" after approving a plan, or asks to go from plan to commit. Orchestrates the full pipeline from approved plan through implementation, simplification, code review, test validation, and pushed commit. All feedback levels are addressed — nothing is deferred.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aaddrick/selkie --skill implement-issue命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | implement-issue |
| description | Use when the user says "implement" after approving a plan, or asks to go from plan to commit. Orchestrates the full pipeline from approved plan through implementation, simplification, code review, test validation, and pushed commit. All feedback levels are addressed — nothing is deferred. |
Execute an approved implementation plan through a quality pipeline that produces a pushed commit. Every stage must complete before advancing. All feedback — critical, warning, and nit — is fixed in every pass.
Core principle: No feedback is deferred. Nits are not optional. The pipeline runs to completion or the commit does not happen.
Not for: Exploration, research, documentation-only tasks, single-line fixes
Plan → Tasks → Implement → Build
→ Simplify → Review → Fix ALL → Build
→ Validate Tests → Fix ALL → Build
→ Re-validate → Commit → Push
STRICT ORDERING: Simplifier before reviewer. Reviewer before validator. Never parallel.
Extract implementation steps from the approved plan. Use TaskCreate for each logical unit. Work through tasks in order, marking in_progress → completed.
Dispatch zig-developer subagent for implementation work, or implement directly if straightforward. After each major step:
zig build && zig build test
If build fails: Fix before continuing. Do not accumulate broken state.
Run zig-code-simplifier over all changed files. This runs FIRST because the reviewer should see clean code.
zig build && zig build test # after simplifier changes
Run zig-code-reviewer over all changed files. In series after simplifier — never parallel.
Fix every finding at every severity level:
| Severity | Action |
|---|---|
| CRITICAL | Fix immediately — blocks merge |
| WARNING | Fix immediately — do not defer |
| NIT | Fix immediately — do not defer |
"Minor" is not "optional." Nits become tech debt. Fix them now.
After fixing:
zig build && zig build test
If the reviewer verdict was REQUEST_CHANGES, re-run zig-code-reviewer to confirm all issues are resolved. Repeat until APPROVE.
Run zig-test-validator over all changed/new test files.
Same rule: fix everything. Remove tautological tests. Add missing coverage. No hollow assertions.
zig build && zig build test
Re-run zig-test-validator. If it still reports issues, fix and re-run. Loop until PASS.
Stage specific files (not git add -A). Commit message format:
<summary referencing issue number> (#N)
<body explaining what was built and any deviations>
Push to origin.
| Mistake | Fix |
|---|---|
| Skip nits — "minor, do later" | Nits are part of the pipeline. Fix now. |
| Simplifier + reviewer parallel | Reviewer must see simplified code. Series only. |
| Commit after fixing without re-validating | Always re-run the agent that found issues. |
| No build between stages | Build after every stage. Catch errors early. |
git add -A | Stage specific files. Avoid committing secrets or artifacts. |
| Forget issue number in commit | Always reference the issue: (#N) |