A pre-commit checklist for checking code quality, tests, documentation, infrastructure changes, and connections between different parts of an application before submitting work.

Use it after coding and testing, before committing or submitting changes. It covers linting, type checks, tests, API changes, database migrations, cross-layer checks, and manual testing.

It helps catch unfinished work, missing documentation, and unverified changes before they reach a shared codebase.

How lxyer/multi-agent-collaboration-system configures Claude Code and

Reuse

Borrowing it

Nothing to install: this file belongs to lxyer/multi-agent-collaboration-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/lxyer/multi-agent-collaboration-system/main/.agents/skills/finish-work/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/lxyer/multi-agent-collaboration-system

Made for: Claude Code, Codex.

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/lxyer/multi-agent-collaboration-system/finish-work/github.svg)](https://agentmods.dev/skills/lxyer/multi-agent-collaboration-system/finish-work)

Your own site

<a href="https://agentmods.dev/skills/lxyer/multi-agent-collaboration-system/finish-work"><img src="https://agentmods.dev/badge/skills/lxyer/multi-agent-collaboration-system/finish-work/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/lxyer/multi-agent-collaboration-system/finish-work"><img src="https://agentmods.dev/badge/skills/lxyer/multi-agent-collaboration-system/finish-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 980 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.00071	$0.00980
Opus 5	$0.00036	$0.00490
Sonnet 5	$0.00014	$0.00196
Haiku 4.5	$0.00007	$0.00098

Measured 8d ago against content hash 4ebb0255d8ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

finish-work 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 8d 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.

.agents/skills/finish-work/SKILL.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Finish Work - Pre-Commit Checklist

Before submitting or committing, use this checklist to ensure work completeness.

Timing: After code is written and tested, before commit

Checklist

1. Code Quality

# Must pass
pnpm lint
pnpm type-check
pnpm test

pnpm lint passes with 0 errors?
pnpm type-check passes with no type errors?
Tests pass?
No console.log statements (use logger)?
No non-null assertions (the x! operator)?
No any types?

2. Code-Spec Sync

Code-Spec Docs:

Does .trellis/spec/backend/ need updates?
- New patterns, new modules, new conventions
Does .trellis/spec/frontend/ need updates?
- New components, new hooks, new patterns
Does .trellis/spec/guides/ need updates?
- New cross-layer flows, lessons from bugs

Key Question:

"If I fixed a bug or discovered something non-obvious, should I document it so future me (or others) won't hit the same issue?"

If YES -> Update the relevant code-spec doc.

2.5. Code-Spec Hard Block (Infra/Cross-Layer)

If this change touches infra or cross-layer contracts, this is a blocking checklist:

Spec content is executable (real signatures/contracts), not principle-only text
Includes file path + command/API name + payload field names
Includes validation and error matrix
Includes Good/Base/Bad cases
Includes required tests and assertion points

Block Rule: If infra/cross-layer changed but the related spec is still abstract, do NOT finish. Run $update-spec manually first.

3. API Changes

If you modified API endpoints:

Input schema updated?
Output schema updated?
API documentation updated?
Client code updated to match?

4. Database Changes

If you modified database schema:

Migration file created?
Schema file updated?
Related queries updated?
Seed data updated (if applicable)?

5. Cross-Layer Verification

If the change spans multiple layers:

Read the full file on GitHub · 149 lines

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.

8d ago First seen · 149 lines · 71 tokens per session scan A 4ebb0255d8ee

Subscribe to this mod's changes

finish-work is a skill published in the GitHub repository lxyer/multi-agent-collaboration-system (1 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 980 once invoked, about $0.0004 per session on Opus 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-08-31.

Multi-Agent ai ai-workflow cli macs terminal

meta-cognition-parallel

An experimental tool for analysing a question or problem in parallel across three layers.

kikakkz/wait-agent · 41 tokens

rust-learner

Use when asking about Rust versions or crate info. Keywords: latest version, what's new, changelog, Rust 1.x, Rust release, stable, nightly, crate info, crates.io, lib.rs, docs.rs, API documentation, crate features, dependencies, which crate, what version, Rust edition, edition 2021, edition 2024, cargo add, cargo…

kikakkz/wait-agent · 123 tokens

rust-router

A routing skill for Rust development questions, including errors, design choices, comparisons, and coding tasks involving Rust tools and packages.

kikakkz/wait-agent · 280 tokens

m07-concurrency

A guide to running work at the same time in Rust, either on threads or through async tasks. It covers shared data, channels, locks, atomics, futures, and common problems such as races and deadlocks.

kikakkz/wait-agent · 75 tokens

m14-mental-model

Use when learning Rust concepts. Keywords: mental model, how to think about ownership, understanding borrow checker, visualizing memory layout, analogy, misconception, explaining ownership, why does Rust, help me understand, confused about, learning Rust, explain like I'm, ELI5, intuition for, coming from Java, coming…

kikakkz/wait-agent · 91 tokens

rust-call-graph

A visualisation tool for Rust function call graphs, showing which functions call one another.

kikakkz/wait-agent · 48 tokens

multi-agent-collaboration-system: Skill for Claude Code