quick-finalize
Close out a change without the deep review loop: stage, simplify code and docs, run the project's checks, smoke test, update the changelog, self-imp…
它会碰到什么
这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。
技能内容
Quick Finalize
Task Tracking
At the start, use TaskCreate to create a task for each phase:
- Run
/stageskill - Run
/simplify-allskill - Run
/run-checksskill - Run
/smoke-testskill - Run
/update-changelogskill - Run
/self-improveskill - Run
/shipskill
Phase 1: Run /stage Skill
Run the /stage skill.
Phase 2: Run /simplify-all Skill
Run the /simplify-all skill on the staged changes (git diff --cached). Stage any edits it makes before continuing.
Phase 3: Run /run-checks Skill
Run the /run-checks skill. Stage any edits it makes before continuing.
Phase 4: Run /smoke-test Skill
Run the /smoke-test skill. It verifies without modifying code, so act on what it reports here: fix each failure and re-run it. When the same failure survives a fix attempt, run the /investigate skill; if investigation finds no root cause, stop and report with its findings. When a blocker cannot be cleared in this session (a path needing real credentials, an external service, or state unavailable here), carry it into Phase 7 so the hand-over names the cases still left to the user, rather than treating it as a failure. Stage any edits before continuing.
Phase 5: Run /update-changelog Skill
Run the /update-changelog skill.
Phase 6: Run /self-improve Skill
Run the /self-improve skill for the current session. Always run this phase even if the session seemed routine. Skip it only when the invocation passed defer-self-improve, meaning a parent workflow continues past this call and closes the session itself.
Phase 7: Run /ship Skill
Run the /ship skill.
Then use the TaskList tool and proceed to any remaining task.
Rules
- Diff size, number of files changed, passing tests, perceived user urgency, or context window concerns are not reasons to skip a phase. Each phase does work beyond what those signals cover. "The session was long" or "a prior phase was thorough" are never valid reasons to skip a later phase.
- Never stage or commit files containing secrets (
.env, credentials, API keys). Warn if detected. - Do not present diffs to the user — the user reviews diffs in an external git client. Use
git diffinternally as needed. - If a non-test phase fails, stop and report the failure. Do not skip ahead.
想直接用这个技能?
本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。
同名技能的其他版本
有 2 个不同仓库或目录里都有叫 quick-finalize 的技能。它们内容并不相同,别混用:
- tobihagemann/turbo — Close out a change without the deep review loop: stage, simplify code and docs, run the pr