A command for closing a coding session by checking the current state, archiving completed tasks, and writing a session journal. It does not create code commits.

Use it when a task is finished to verify the state, optionally archive other completed tasks, and record the session's progress.

It separates end-of-session record keeping from the earlier workflow step where code is committed.

How belingud/yaicli configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to belingud/yaicli. 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/belingud/yaicli/master/.claude/commands/trellis/finish-work.md

Clone the repo

git clone --depth 1 https://github.com/belingud/yaicli

Made for: Claude Code.

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/commands/belingud/yaicli/finish-work/github.svg)](https://agentmods.dev/commands/belingud/yaicli/finish-work)

Your own site

<a href="https://agentmods.dev/commands/belingud/yaicli/finish-work"><img src="https://agentmods.dev/badge/commands/belingud/yaicli/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/commands/belingud/yaicli/finish-work"><img src="https://agentmods.dev/badge/commands/belingud/yaicli/finish-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 836 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 100% copy Near-identical to another mod 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.00000	$0.00836
Opus 5.5	$0.00000	$0.00334
Sonnet 5.5	$0.00000	$0.00167
Haiku 4.5	$0.00000	$0.00084

Measured 5d ago against content hash d6aa570ab684, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 5d 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.

Origin

This is a copy

100% identical to finish-work — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/trellis/finish-work.md · 67 lines

How it starts

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

Finish Work

Wrap up the current session: archive the active task (and any other completed-but-unarchived tasks the user wants to clean up) and record the session journal. Code commits are NOT done here — those happen in workflow Phase 3.4 before you invoke this command.

Step 1: Survey current state

python3 ./.trellis/scripts/get_context.py --mode record

This prints:

My active tasks — review whether any besides the current one are actually done (code merged, AC met) and should be archived this round.
Git status — quick visual on what's dirty.
Recent commits — you'll need their hashes in Step 4 for --commit.

If --mode record surfaces other completed tasks not tied to the current session, surface them to the user with a one-shot confirmation: "These N tasks look done — archive them too in this round? [y/N]". Default is no; the current active task is always archived in Step 3 regardless.

Step 2: Sanity check — classify dirty paths

Run:

git status --porcelain

Filter out paths under .trellis/workspace/ and .trellis/tasks/ — those are managed by add_session.py and task.py archive auto-commits and will appear dirty as part of this skill's own work.

For each remaining dirty path, decide whether it belongs to the current task or to other parallel work (e.g., another terminal window editing the same repo). Heuristics:

Paths referenced in the current task's prd.md / implement.jsonl / check.jsonl → current task
Paths in code areas matching the task's stated scope, or that you remember editing this session → current task
Paths in unrelated areas you have no recollection of touching this session → other parallel work

Then route:

Any remaining path looks like current-task work — bail out with:

"Working tree has uncommitted code changes from this task: <list>. Return to workflow Phase 3.4 to commit them before running /trellis:finish-work."

Do NOT run git commit here. Do NOT prompt the user to commit. The user goes back to Phase 3.4 and the AI drives the batched commit there.
All remaining paths look unrelated (other parallel-window work) — report them once and continue to Step 3:

"FYI, dirty files outside this task's scope — leaving them for the other window: <list>."
Genuinely unsure — ask the user once: "Are <list> this task's work I forgot to commit, or another window's? (commit / ignore)" — then route per their answer.

Read the full file on GitHub · 67 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.

5d ago First seen · 67 lines · 0 tokens per session scan A d6aa570ab684

Subscribe to this mod's changes

finish-work is a command published in the GitHub repository belingud/yaicli (19 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 836 tokens. A static security scan graded it A with 0 findings. It is 100% identical to finish-work, differing in 0 lines, and is treated as a copy.

Git and workflow LLM Planning Python chatgpt cli gpt typer

finish-work next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
finish-workbelingud/yaicli	Command	19	yesterday	Apache-2.0	A	0	Claude Code
fix-issuescan1357/oh-my-pi	Command	38k	yesterday	MIT	A	0	Claude Code
AGENTSlanggenius/dify	Command	160k	yesterday	none	A	0	Claude Code
prechoVic/blade-code	Command	181	24d ago	MIT	A	3	Claude Code
commitechoVic/blade-code	Command	181	24d ago	MIT	A	8	Claude Code
git-commitChatLunaLab/chatluna	Command	446	9d ago	AGPL-3.0	A	4	Claude Code
clean_goneronmkr/PromptBook	Command	2	5mo ago	Apache-2.0	A	31	Claude Code

yaicli: Command for Claude Code