Mise
majiayu000/claude-skill-registry
Manages per-project tool versions (Node.js, Python, Go, Rust, Ruby and hundreds more), environment variables and tasks from one mise.toml file, as a single binary that replaces nvm, pyenv, rbenv and…
Finalize a merge request: rebase onto main, run bugs, simplify, and specs in parallel, apply, then refactor last.
Install Finalize
$ npx skills add zifeo/lade --skill finalize -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install zifeo/lade 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/zifeo/lade.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/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/zifeo/lade/tree/main/.cursor/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/zifeo/lade/tree/main/.cursor/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 zifeo/lade --skill finalize -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install zifeo/lade finalize --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zifeo/lade.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/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/zifeo/lade/tree/main/.cursor/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 zifeo/lade --skill finalize -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install zifeo/lade finalize --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zifeo/lade.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/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/zifeo/lade/tree/main/.cursor/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/zifeo/lade.git --path .cursor/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 zifeo/lade --skill finalize -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install zifeo/lade finalize --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zifeo/lade.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/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/zifeo/lade/tree/main/.cursor/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 zifeo/lade 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 zifeo/lade --skill finalize -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/zifeo/lade.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/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/zifeo/lade/tree/main/.cursor/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 zifeo/lade --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 zifeo/lade finalize --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/zifeo/lade.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/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/zifeo/lade/tree/main/.cursor/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
- 133
- Token cost
- ~1k tokens
- SKILL.md length
- 574 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Finalize a merge request: rebase onto main, run bugs, simplify, and specs in parallel, apply, then refactor last.
- Works in 5 steps: Sit on main first → Parallel: bugs, simplify, specs → Last: refactor → …
- The user asks to finalize
- SKILL.md covers When, 0. Sit on main first, 1. Parallel: bugs, simplify,… and 2. Last: refactor, plus 2 more sections
- Calls git
What it does
Finalize is an agent skill from zifeo/lade. Finalize a merge request: rebase onto main, run bugs, simplify, and specs in parallel, apply, then refactor last. Use when the user asks to finalize, close a PR, or run the review pageant.
Its SKILL.md is about 1k 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 DevOps & Cloud, covering Refactoring and Secrets management. It works with Bash, Kubernetes and Rust. The repository describes itself as: Temporary access to secrets and private networks for one command, then gone. Same wrap for humans and agents. See which access was used. The licence is MPL-2.0.
When your agent uses it
- The user asks to finalize
- Run the review pageant
Example prompts
- “/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 d775ef5. 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 1k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 574 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 passed
The automated check found no risky patterns in SKILL.md.
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 zifeo/lade at commit d775ef5, republished under its MPL-2.0 licence (© zifeo). 574 words, ~1,019 tokens.
Download SKILL.mdSave it as
.claude/skills/finalize/SKILL.md (or your agent's skills folder).- name
- finalize
- description
- Finalize a merge request: rebase onto main, run bugs, simplify, and specs in parallel, apply, then refactor last. Use when the user asks to finalize, close a PR, or run the review pageant.
- disable-model-invocation
- true
Finalize
A pageant, not a swarm. Reviewers are read-only. The parent waits, edits, then launches the next seat. One pass.
When
User says /finalize, finalize, close the MR, or ready to merge.
Do not run this on a drive-by question.
0. Sit on main first
Fetch origin/main. Rebase this branch onto it (or merge main if
rebase is refused). If the rebase conflicts, stop and ask. Do not
launch reviewers on a stale base.
Then pin what will be reviewed. Commits ahead of origin/main and
uncommitted edits both count. A dirty tree is the review subject.
Do not commit it to make a range. Stop only when both are empty.
git fetch origin main
git merge-base origin/main HEAD
git diff --stat "$(git merge-base origin/main HEAD)"
git diff --stat HEADBuild a Spec: block for the specs child, in this order:
- Specs the user stated in this conversation
- The PR body / issue, if this is an MR
- A file the user named as the spec
If none of those exist, still launch specs. It must ask. Do not drop the seat.
The child scope uses Diff: branch changes when the commit range is
non-empty, and Diff: uncommitted changes when the work is only in
the tree. When both exist, name both.
Full Repository Path: <abs>
Diff: <branch changes | uncommitted changes | both>
Base Branch: main
Range: <merge-base>...<HEAD>
Worktree: <clean | dirty, include HEAD>
Spec:
<quoted lines, or "none, ask">Custom agent names may be missing on the Task tool. Default path:
generalPurpose children. Paste .cursor/agents/<name>.md as the
preamble, then the scope block.
1. Parallel: bugs, simplify, specs
Launch these three together. Wait for all three. Do not launch
refactor here.
| Subagent | Job | Writes |
|---|---|---|
bugs | Concrete failures | no |
simplify | Smaller form, same behavior | no |
specs | Diff vs a cited spec. Asks if no reference | no |
If specs returns Ask:, answer from this conversation or ask
the user. Then relaunch only specs once with the answer.
Do not invent product.
Apply only if useful. Useful means a real failure, or a
call site that should have used an existing helper for the
same concern. Not useful: taste, a new generic, or a wc -l
move that does not change how a human reads production code.
- bugs critical and high, if the failure is real.
- specs
wrong/missingthat cite a reference. - simplify reuse of a named existing helper, or a dead wrapper with one caller. Do not extract a new helper as a leftover. Hunt the project, not only the hunk.
Narrowest check that proves the edit. Use the project's usual check. Do not widen permissions to make a build pass.
Show full SKILL.md (177 more words)Show less
2. Last: refactor
Only after step 1 is applied. Launch refactor alone.
| Subagent | Job | Writes |
|---|---|---|
refactor | Files over 300 (soft) / 350 (hard), including markdown | no |
Apply a hard file only if the split is two jobs a human
can hold (production code). Moving tests to another file only
to get under the line limit is not useful. Soft (301–350)
is a proposal; apply only if the split is obvious and local.
Keep the public API and test names.
Narrowest check again.
3. Do not
- Commit, push, merge, or enable auto-merge
- Request
allfor a compile - Launch refactor next to bugs
- Let specs invent a contract
- Mention source control unless the user asked
4. Report
One short status. Then leftovers as a table, only rows where
Useful? is yes:
| Item | Useful? | Why |
|---|
Useful? is yes only for a real failure or an existing
helper to call. Skip taste, new helpers, and wc -l moves.
A leftover is only a still-real failure or a named existing
helper the diff still misses. "The reviewer mentioned it" is
not a leftover.
© zifeo, MPL-2.0. 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 .cursor/skills/finalize of zifeo/lade.
Open the folder on GitHubat commit d775ef5
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 skillzifeo/lade | 133 | — | ~1k | Automated safety check: Pass | MPL-2.0 | |
| Misemajiayu000/claude-skill-registry | 666 | 1 repos | ~1.8k | Automated safety check: Notes | Apache-2.0 | |
| Niubashunixwin/niubash | 155 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Kopiur Designhome-operations/kopiur | 113 | — | ~2.4k | Automated safety check: Pass | AGPL-3.0 | |
| Flow Contextflowexec/flow | 137 | — | ~654 | Automated safety check: Pass | Apache-2.0 | |
| Refactoratilladeniz/Kubeli | 387 | — | ~7.7k | Automated safety check: Warn | MIT |
Similar skills
Niubash
unixwin/niubash
Run Windows tasks in Niubash, the GNU Bash-compatible Windows-native shell.
Kopiur Design
home-operations/kopiur
Design norms and locked decisions for the Kopiur Kopia-native Kubernetes backup operator (Rust/kube-rs).
Flow Context
flowexec/flow
This project uses flow for automation. An agent skill from flowexec/flow.
Refactor
atilladeniz/Kubeli
Refactors code following Ousterhout's design principles. An agent skill from atilladeniz/Kubeli.
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
More from zifeo/lade
Lade Release
zifeo/lade
Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version.
Related
Works with
Categories
Questions about Finalize
What does Finalize do?
Finalize a merge request: rebase onto main, run bugs, simplify, and specs in parallel, apply, then refactor last. Finalize is an agent skill from zifeo/lade. Finalize a merge request: rebase onto main, run bugs, simplify, and specs in parallel, apply, then refactor last.
When should I use Finalize?
Finalize fits situations like: the user asks to finalize; run the review pageant.
How do I install Finalize in Claude Code?
Run `npx skills add zifeo/lade --skill finalize -a claude-code`. Or copy the skill folder (.cursor/skills/finalize in zifeo/lade) 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 zifeo/lade --skill finalize -a codex`. Or copy the skill folder (.cursor/skills/finalize in zifeo/lade) 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 zifeo/lade --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 no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Finalize use?
Finalize is published under the MPL-2.0 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 1k tokens (SKILL.md is roughly 4.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 Finalize?
Skills that share tags, products or a category with Finalize: Mise (majiayu000/claude-skill-registry, 666 stars), Niubash (unixwin/niubash, 155 stars), Kopiur Design (home-operations/kopiur, 113 stars) and Flow Context (flowexec/flow, 137 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Finalize?
zifeo (a GitHub user) maintains it in zifeo/lade, which has 133 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: zifeo/lade on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.