Reproduce Chat States
different-ai/openwork
Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit.
Install Finalize
$ npx skills add tobihagemann/turbo --skill finalize -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tobihagemann/turbo finalize --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/finalize .claude/skills/finalize && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/finalize into .claude/skills/finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finalize", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tobihagemann/turbo/tree/main/codex/skills/finalizeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tobihagemann/turbo --skill finalize -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tobihagemann/turbo finalize --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/codex/skills/finalize .agents/skills/finalize && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/finalize into .agents/skills/finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finalize", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill finalize -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tobihagemann/turbo finalize --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/codex/skills/finalize .cursor/skills/finalize && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/finalize into .cursor/skills/finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finalize", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tobihagemann/turbo.git --path codex/skills/finalize--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tobihagemann/turbo --skill finalize -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tobihagemann/turbo finalize --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/codex/skills/finalize .gemini/skills/finalize && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/finalize into .gemini/skills/finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finalize", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tobihagemann/turbo finalizeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tobihagemann/turbo --skill finalize -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/codex/skills/finalize .github/skills/finalize && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/finalize into .github/skills/finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finalize", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill finalize -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tobihagemann/turbo finalize --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/codex/skills/finalize .opencode/skills/finalize && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/finalize into .opencode/skills/finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "finalize", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
finalize- GitHub stars
- 407
- Token cost
- ~1.3k tokens
- SKILL.md length
- 720 words
- Files
- 1
- Skills in repo
- 81
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit.
- Works in 5 steps: Run $polish-code Skill → Run $simplify-docs Skill → Run $update-changelog Skill → …
- The user asks to finalize implementation
- SKILL.md covers Task Tracking, Phase 1: Run $polish-code Skill, Phase 2: Run $simplify-docs… and Phase 3: Run $update-changelog…, plus 3 more sections
- Calls git
What it does
Finalize is an agent skill from tobihagemann/turbo. Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.
When your agent uses it
- The user asks to finalize implementation
- Finalize changes
- Wrap up implementation
- Ready to commit
Example prompts
- “finalize implementation”
- “finalize changes”
- “wrap up implementation”
- “/finalize”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4b9f4cf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Finalize loads about 1.3k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 720 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:76
age or commit files containing secrets (`.env`, credentials, API keys). Warn if detected.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tobihagemann/turbo at commit 4b9f4cf, republished under its MIT licence (© tobihagemann). 720 words, ~1,297 tokens.
Download SKILL.mdSave it as
.claude/skills/finalize/SKILL.md (or your agent's skills folder).- name
- finalize
- description
- Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
Finalize Implementation
Post-implementation QA workflow: tests, code polishing, commit, and self-improvement.
Task Tracking
At the start, use update_plan to track each phase, restating any remaining steps of a parent workflow alongside them:
- Run
$polish-codeskill - Run
$simplify-docsskill - Run
$update-changelogskill - Run
$self-improveskill - Ship It
Workflow 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.
Phase 1: Run $polish-code Skill
Run the $polish-code skill for the current changes.
Phase 2: Run $simplify-docs Skill
Run the $simplify-docs skill on the staged changes (git diff --cached). Stage any edits it makes before continuing.
Phase 3: Run $update-changelog Skill
Run the $update-changelog skill. Stage any edits it makes before continuing.
Phase 4: Run $self-improve Skill
Run the $self-improve skill for the current session. Always run this phase even if the session seemed routine.
Phase 5: Ship It
Step 1: Analyze Split
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.
Run git diff --cached --stat and git diff --cached to understand the scope. Categorize changes along three dimensions:
- Concern type: refactoring, bug fix, new feature, cleanup, dependency update
- Layer/domain: backend, frontend, database migrations, i18n, tests, configuration
- Logical unit: files that form a coherent, independently reviewable change
A split is warranted when the staged changes contain multiple reviewable units. Each unit should be independently understandable, testable, and revertable. When deciding group boundaries, consider whether a reviewer could evaluate each group without needing context from the others.
Show full SKILL.md (260 more words)Show less
Step 2: Present Analysis and Choose Path
Output the split analysis as text.
If changes form a single cohesive unit, note this and run the $ship skill.
If changes span multiple reviewable units, propose an ordered list of groups. For each group, specify:
- Name and one-line description
- File list (flag files with mixed-concern hunks)
- Dependencies: which earlier groups, if any, this group builds on
Use request_user_input to let the user choose whether to ship the changes together or split them up.
- Ship together — ship all staged changes as one unit; run the
$shipskill - Split up — ship each group as its own unit; run the
$split-and-shipskill
If this run created a goal, follow the closing update_plan call below by mirroring it into the workflow file, setting Status: closed, and marking the goal complete with update_goal, in that order. Then call update_plan to mark this step completed and continue with the next step of the active workflow.
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 step fails (polish, review), stop and report the failure. Do not skip ahead.
© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in codex/skills/finalize of tobihagemann/turbo.
Open the folder on GitHubat commit 4b9f4cf
Compare with similar skills
Finalize next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Finalize this skilltobihagemann/turbo | 407 | — | ~1.3k | Automated safety check: Notes | MIT | |
| Reproduce Chat Statesdifferent-ai/openwork | 24k | — | ~673 | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Minimal Run And Auditlllllllama/RigorPilot-Skills | 497 | 2 repos | ~691 | Automated safety check: Pass | MIT | |
| Moav E2EMotherofallVPNs/MoaV | 448 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Anchor Reprolynxlangya/techne | 105 | 1 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Minimal Run And Audit
lllllllama/RigorPilot-Skills
Rigor Run skill for README-first deep learning repo reproduction.
Moav E2E
MotherofallVPNs/MoaV
Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.
Anchor Repro
lynxlangya/techne
Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.
Creating A Coral Task
Human-Agent-Society/CORAL
Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…
More from tobihagemann/turbo
All 81 skills in this repoConsult Oracle
tobihagemann/turbo
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.
Fetch PR Comments
tobihagemann/turbo
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.
Recall Rationale
tobihagemann/turbo
Recall why a past change was made by locating the Claude Code transcript that produced it.
Codex Exec
tobihagemann/turbo
Run autonomous task execution using the codex CLI. An agent skill from tobihagemann/turbo.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Investigate
tobihagemann/turbo
Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps.
Related
Categories
Questions about Finalize
What does Finalize do?
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Finalize is an agent skill from tobihagemann/turbo. Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit.
When should I use Finalize?
Finalize fits situations like: the user asks to finalize implementation; finalize changes; wrap up implementation; ready to commit.
How do I install Finalize in Claude Code?
Run `npx skills add tobihagemann/turbo --skill finalize -a claude-code`. Or copy the skill folder (codex/skills/finalize in tobihagemann/turbo) into .claude/skills/finalize in your project. Claude Code loads it when a task matches its description.
How do I install Finalize in Codex?
Run `npx skills add tobihagemann/turbo --skill finalize -a codex`. Or copy the skill folder (codex/skills/finalize in tobihagemann/turbo) into .agents/skills/finalize in your project. Codex loads it when a task matches its description.
Can I use Finalize in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill finalize -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/finalize, .gemini/skills/finalize, .github/skills/finalize and .opencode/skills/finalize in your project.
What does Finalize need to run?
Going by SKILL.md and its folder, Finalize needs the command-line tools its instructions call (git).
Does Finalize access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Finalize safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Finalize use?
Finalize is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Finalize use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Finalize?
Skills that share tags, products or a category with Finalize: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Minimal Run And Audit (lllllllama/RigorPilot-Skills, 497 stars) and Moav E2E (MotherofallVPNs/MoaV, 448 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Finalize?
tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 407 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 2026.
Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.