trellis-finish-work

Archives completed tasks and records session journals after verifying the git working tree.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a coding session cleanly requires several easy-to-forget steps: confirming all work is committed, archiving finished tasks, and writing a session journal. This Skill automates that wrap-up sequence so nothing is left uncommitted or undocumented. ## Core Features & Use Cases - Dirty-tree classification: Inspects git status --porcelain, filters out Trellis-managed paths, and decides whether remaining changes belong to the current task or parallel work, blocking the wrap-up if uncommitted task code exists. - Task archiving: Archives the active task (plus any user-confirmed completed tasks) via task.py archive, producing automatic chore(task): archive commits. - Session journaling: Records a session entry with title, commit hashes, and summary through add_session.py, producing a chore: record journal commit. - Use Case: After finishing a feature and committing code in workflow Phase 3.4, run this Skill to archive the task and log the session journal in the correct commit order. ## Quick Start Ask the AI to finish the current Trellis work session by archiving the active task and recording the session journal.

Frequently Asked Questions about trellis-finish-work

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

FAQPage Schema
How do I wrap up a Trellis coding session?▼

Run the finish-work flow after committing code in Phase 3.4. It surveys active tasks with get_context.py, archives completed tasks via task.py archive, and records a session journal with add_session.py including the work commit hashes.

How to archive a completed task in Trellis?▼

Run python3 ./.trellis/scripts/task.py archive <task-name>. Each archive produces an automatic chore(task): archive commit. The finish-work skill archives the current active task plus any extra completed tasks the user confirms.

Why does finish-work refuse to run with a dirty git tree?▼

It blocks when uncommitted changes appear to belong to the current task, because code commits must happen in workflow Phase 3.4 before wrap-up. Paths under .trellis/workspace/ and .trellis/tasks/ are excluded since Trellis scripts manage them.

Does finish-work create git commits for my code changes?▼

No. It never commits code changes itself; it only produces chore(task): archive and chore: record journal commits through the Trellis scripts. Uncommitted task code sends you back to Phase 3.4 to commit first.

What commit order does the session journal produce?▼

The final git log order is work commits from Phase 3.4 first, then one or more chore(task): archive commits, then the chore: record journal commit. Archive commit hashes are excluded from the journal's --commit argument.