A completion workflow for coding tasks that checks changes, commits them, runs project checks, rebases when needed, and reviews the result. It also describes what to do when there is nothing to finish.

Use it after modifying code when you need a structured sequence for committing, testing, rebasing, and reviewing the work.

It provides a repeatable handoff process so changes are checked and the repository is left in a known state.

finish — Skill for Claude Code by motlin/claude-code-plugins

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add motlin/claude-code-plugins --skill finish

Clone the repo

git clone --depth 1 https://github.com/motlin/claude-code-plugins

Made for: Claude Code.

Or install orchestration, the plugin that ships this one along with the rest of its 5 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/motlin/claude-code-plugins/finish/github.svg)](https://agentmods.dev/skills/motlin/claude-code-plugins/finish)

Your own site

<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/finish"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/finish/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/finish"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/finish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 205 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.00205
Opus 5.5	$0.00014	$0.00082
Sonnet 5.5	$0.00007	$0.00041
Haiku 4.5	$0.00003	$0.00020

Measured 9d ago against content hash 5e96658fdec5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

finish scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/orchestration/skills/finish/SKILL.md · 18 lines

What it actually says

Finish Workflow

If the working tree is clean and there is nothing to verify, report that there is nothing to finish.

Use the caller's prompt as the commit intent. Run every applicable step, in order:

Commit with the git:commit skill, distilling the caller's prompt into a single-line message. Commit before precommit because git test run HEAD refuses a dirty tree and tests the committed HEAD.
Run the build:precommit skill. Cached successes pass quickly.
Rebase with the git:git-rebase skill.
Review the committed diff for reuse, quality, and efficiency, and make cleanup changes when warranted.
If cleanup changed anything, create a fixup commit for HEAD.
Run the build:precommit skill again.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago Changed · -10 tokens per session 5e96658fdec5
22d ago Changed · -6 lines · +10 tokens per session 8a2f85a16606
1mo ago Changed dfccd80954a6
1mo ago First seen · 24 lines · 34 tokens per session scan A 7d5213eb472b

Subscribe to this mod's changes

finish is a skill published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 205 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Building agents Commits Git and workflow

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens

git-commit

Generate well-formatted git commit messages following conventional commit standards.

ThinkInAIXYZ/deepchat · 15 tokens

repo-sync

Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.

davidondrej/skills · 25 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

contributing

How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…

HugoRCD/evlog · 68 tokens

engineer-bot-ops

A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.

makecindy/cindy · 57 tokens