Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/finalize
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit.
Passed 2 of 8 test cases with the skill, and 2 of 8 without it.
and 1 more in the full report
4 fixed1 passed either way13 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where should active loop state be maintained during the finalization workflow?
| Checked | Without skill | With skill |
|---|---|---|
| Refers to .turbo/loops/ as the directory for loop state. | Missed | Passed |
The instructions your model reads when the skill loads.
Post-implementation QA workflow: tests, code polishing, commit, and self-improvement.
At the start, use update_plan to track each phase, restating any remaining steps of a parent workflow alongside them:
$polish-code skill$simplify-docs skill$update-changelog skill$self-improve skillWorkflow state lives at .turbo/workflows/<slug>.md — slug from the governing plan when one is in context, otherwise the current branch name with non-alphanumerics replaced by hyphens. It pairs one-to-one with the thread's goal. When this run's create_goal attempt succeeds, write the file fresh: Status: active plus this invocation's update_plan list as a checkbox list. When an unfinished goal already exists, mirror into the workflow file its objective names; when it names none, continue without workflow state. Mirror every update_plan call into the file; it holds the pipeline's remaining steps and their statuses. When this run created the goal, run the terminal step in order: mark the final entry completed and mirror it, set Status: closed, mark the goal complete with update_goal, then emit any halt message.
Then attempt create_goal with the objective: "Run $finalize post-implementation QA on the staged changes through Phase 5 (Ship It). Workflow state: .turbo/workflows/<slug>.md; mirror every update_plan call into it. Loop state lives under .turbo/loops/. After any context compaction, re-read the workflow file and any active ledger, and continue from the first unfinished entry. Mark this goal complete when Phase 5 finishes." If an unfinished goal already exists, an outer workflow owns it; continue without creating one.
$polish-code SkillRun the $polish-code skill for the current changes.
$simplify-docs SkillRun the $simplify-docs skill on the staged changes (git diff --cached). Stage any edits it makes before continuing.
$update-changelog SkillRun the $update-changelog skill.
$self-improve SkillRun the $self-improve skill for the current session. Always run this phase even if the session seemed routine.
Examine the staged changes and evaluate whether they form a single reviewable unit or several independently reviewable units. This step decides only whether to split; the chosen ship skill owns all repository-state detection and the commit, push, branch, and PR intent.
test cases passed, vs 2 / 8 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.