trellis-finish-work

Archives completed Trellis tasks, records session journals, and commits bookkeeping changes.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/SilentFlower/flower-trellis --skill trellis-finish-work-silentflower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-finish-work
Source: https://github.com/SilentFlower/flower-trellis/tree/main/.agents/skills/trellis-finish-work
Command: npx skills add https://github.com/SilentFlower/flower-trellis --skill trellis-finish-work-silentflower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a coding session involves error-prone bookkeeping: verifying task completion, reviewing decisions, archiving task directories, writing session journals, and committing or pushing those changes without touching unrelated work. This Skill automates that exact bookkeeping workflow with strict safety gates. ## Core Features & Use Cases - Completion and Decision Gates: Verifies the task status is completed via task_progress.py and audits the decision log, blocking archival when decisions are unreviewed or the log is corrupt. - Scoped Archive and Journal: Runs task.py archive and add_session.py, then creates one scoped Git commit containing only the exact archive, journal, and child task.json paths. - Conditional Push: Pushes the bookkeeping commit only when the branch was synchronized with its upstream at session start; otherwise keeps changes local and reports why. - Use Case: After finishing a feature task in a Trellis-managed project, invoke this Skill to archive the task, log the session, and safely commit the bookkeeping without disturbing other in-progress work. ## Quick Start Ask the assistant to finish the current Trellis work session and archive the completed task.

Frequently Asked Questions about trellis-finish-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive a completed Trellis task at the end of a session?▼

Run the finish-work workflow, which verifies the task status is completed via task_progress.py, audits the decision log, then runs task.py archive and add_session.py. It commits only the exact archive and journal paths in one scoped bookkeeping commit.

What happens if my task has unreviewed decisions before archiving?▼

The decision audit lists each unreviewed decision with its ID, topic, choice, rationale, risk, and verification, then waits for one explicit review. You can accept all decisions or request changes, which stops archival and returns the task for rework.

Does finish-work push commits to the remote automatically?▼

It pushes only when the branch was synchronized with its upstream at session start and the only new commit is the bookkeeping commit. If the branch was ahead, behind, diverged, or lacked an upstream, the commit stays local and the reason is reported.

Why does finish-work stop instead of archiving my task?▼

It fails closed when the task is not marked completed, the decision log is corrupt, Git is in a detached HEAD or conflicted state, or the auto-loop handoff cannot be validated. It never recommits business code or manufactures completion.

Can finish-work touch files from other tasks or windows?▼

No. It stages only the exact archive destination, changed child task.json files, and journal paths from the current invocation. Unrelated dirty or staged paths are left untouched and reported separately in the final result.