Release
akitaonrails/my-skills
Cut and publish a project release — verify or derive the version number (patch/minor/major) from the changelog and accumulated changes, follow the repo's own branch and versioning strategy, rebase…
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-improve, and ship.
Install Quick Finalize
$ npx skills add tobihagemann/turbo --skill quick-finalize -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tobihagemann/turbo quick-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/quick-finalize .claude/skills/quick-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 "quick-finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/quick-finalize into .claude/skills/quick-finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-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/quick-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 quick-finalize -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tobihagemann/turbo quick-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/quick-finalize .agents/skills/quick-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 "quick-finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/quick-finalize into .agents/skills/quick-finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-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 quick-finalize -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tobihagemann/turbo quick-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/quick-finalize .cursor/skills/quick-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 "quick-finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/quick-finalize into .cursor/skills/quick-finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-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/quick-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 quick-finalize -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tobihagemann/turbo quick-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/quick-finalize .gemini/skills/quick-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 "quick-finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/quick-finalize into .gemini/skills/quick-finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-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 quick-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 quick-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/quick-finalize .github/skills/quick-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 "quick-finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/quick-finalize into .github/skills/quick-finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-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 quick-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 quick-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/quick-finalize .opencode/skills/quick-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 "quick-finalize" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/quick-finalize into .opencode/skills/quick-finalize/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "quick-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
quick-finalize- GitHub stars
- 407
- Token cost
- ~1.5k tokens
- SKILL.md length
- 866 words
- Files
- 1
- Skills in repo
- 81
- Repo updated
- First seen
- Licence
- MIT
At a glance
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-improve, and ship.
- Works in 7 steps: Run $stage Skill → Run $simplify-all Skill → Run $run-checks Skill → …
- The user asks to quick finalize
- SKILL.md covers Task Tracking, Phase 1: Run $stage Skill, Phase 2: Run $simplify-all Skill and Phase 3: Run $run-checks Skill, plus 5 more sections
- Calls git
What it does
Quick Finalize is an agent skill from tobihagemann/turbo. 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-improve, and ship. Use when the user asks to "quick finalize", "quickly finalize", "finalize quickly", "light finalize", "wrap this up quickly", "close this out without the full review", or "ship this without the deep pass".
Its SKILL.md is about 1.5k 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, Changelog and release notes and Code simplification. 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 quick finalize
- Quickly finalize
- Finalize quickly
- Wrap this up quickly
Example prompts
- “quick finalize”
- “quickly finalize”
- “finalize quickly”
- “/quick-finalize”
Workflow steps
7 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
Quick Finalize loads about 1.5k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 866 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:84
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). 866 words, ~1,520 tokens.
Download SKILL.mdSave it as
.claude/skills/quick-finalize/SKILL.md (or your agent's skills folder).- name
- quick-finalize
- description
- 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-improve, and ship. Use when the user asks to "quick finalize", "quickly finalize", "finalize quickly", "light finalize", "wrap this up quickly", "close this out without the full review", or "ship this without the deep pass".
Quick Finalize
Task Tracking
At the start, use update_plan to track each phase, restating any remaining steps of a parent workflow alongside them:
- Run
$stageskill - Run
$simplify-allskill - Run
$run-checksskill - Run
$smoke-testskill - 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 $quick-finalize on the current changes through Phase 7 (Ship It). Workflow state: .turbo/workflows/<slug>.md; mirror every update_plan call into it. After any context compaction, re-read the workflow file and continue from the first unfinished entry. Mark this goal complete when Phase 7 finishes." If an unfinished goal already exists, an outer workflow owns it; continue without creating one.
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 to the end of the run and name it in the closing report as a case still left to the user, rather than treating it as a failure. Write it into the workflow file too, as a Left to the user: line below the checklist, and keep that line through every later mirror. When a fix made here edited code, run the $run-checks skill again once no failure remains. Stage any edits before continuing.
Phase 5: Run $update-changelog Skill
Run the $update-changelog skill. Stage any edits it makes before continuing.
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.
Phase 7: Ship It
Show full SKILL.md (388 more words)Show less
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.
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 phase fails, 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/quick-finalize of tobihagemann/turbo.
Open the folder on GitHubat commit 4b9f4cf
Compare with similar skills
Quick 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 |
|---|---|---|---|---|---|---|
| Quick Finalize this skilltobihagemann/turbo | 407 | — | ~1.5k | Automated safety check: Notes | MIT | |
| Releaseakitaonrails/my-skills | 212 | — | ~1.9k | Automated safety check: Pass | None | |
| Ship Web Gamesnirholas/three.ws | 227 | 1 repos | ~284 | Automated safety check: Pass | Apache-2.0 | |
| Plugin Improveglittercowboy/plugin-freedom-system | 216 | — | ~4.2k | Automated safety check: Notes | None | |
| Repomatic Depskdeldycke/dotfiles | 173 | — | ~7.3k | Automated safety check: Notes | BSD-2-Clause | |
| Codex Plugin QAcode-yeongyu/oh-my-openagent | 70k | 1 repos | ~1.9k | Automated safety check: Pass | Custom licence |
Similar skills
Ship Web Games
nirholas/three.ws
Package, deploy, and verify a playable Three.js or web game.
Plugin Improve
glittercowboy/plugin-freedom-system
Fix bugs, add features to completed plugins. An agent skill from glittercowboy/plugin-freedom-system.
Repomatic Deps
kdeldycke/dotfiles
Generate dependency graphs. An agent skill from kdeldycke/dotfiles.
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
OpenWork Desktop CDP Driver
different-ai/openwork
Drives a running OpenWork desktop window over CDP from the shell to evaluate JS, take screenshots, start sessions and send prompts for hand checks.
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 Quick Finalize
What does Quick Finalize do?
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-improve, and ship. Quick Finalize is an agent skill from tobihagemann/turbo. 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-improve, and ship.
When should I use Quick Finalize?
Quick Finalize fits situations like: the user asks to quick finalize; quickly finalize; finalize quickly; wrap this up quickly.
How do I install Quick Finalize in Claude Code?
Run `npx skills add tobihagemann/turbo --skill quick-finalize -a claude-code`. Or copy the skill folder (codex/skills/quick-finalize in tobihagemann/turbo) into .claude/skills/quick-finalize in your project. Claude Code loads it when a task matches its description.
How do I install Quick Finalize in Codex?
Run `npx skills add tobihagemann/turbo --skill quick-finalize -a codex`. Or copy the skill folder (codex/skills/quick-finalize in tobihagemann/turbo) into .agents/skills/quick-finalize in your project. Codex loads it when a task matches its description.
Can I use Quick 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 quick-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/quick-finalize, .gemini/skills/quick-finalize, .github/skills/quick-finalize and .opencode/skills/quick-finalize in your project.
What does Quick Finalize need to run?
Going by SKILL.md and its folder, Quick Finalize needs the command-line tools its instructions call (git).
Does Quick 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 Quick 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 Quick Finalize use?
Quick 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 Quick Finalize use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Quick Finalize?
Skills that share tags, products or a category with Quick Finalize: Release (akitaonrails/my-skills, 212 stars), Ship Web Games (nirholas/three.ws, 227 stars), Plugin Improve (glittercowboy/plugin-freedom-system, 216 stars) and Repomatic Deps (kdeldycke/dotfiles, 173 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Quick 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.