trellis-finish-work

Name: trellis-finish-work
Availability: InStock
Author: Herbivore

Archive completed Trellis tasks and record a session journal after verifying quality gates.

92|8|Updated May 15, 2026

Search Tags:#workflow automation #git workflow #quality gate #trellis #session wrap-up #task archiving #session journal

Ready to run

npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill trellis-finish-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trellis-finish-work
Source: https://github.com/LonelyHerbivore/Trellis-Herbivore/tree/main/.agents/skills/trellis-finish-work
Command: npx skills add https://github.com/LonelyHerbivore/Trellis-Herbivore --skill trellis-finish-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you safely end a Trellis-driven coding session by verifying quality gates, archiving finished tasks, and recording what happened—without incorrectly committing or mixing unrelated work from other terminals.

Core Features & Use Cases

Current-state survey: Inspects active tasks, git status, and recent work-commit hashes so you can close out the right scope.
Dirty-path classification guardrails: Detects uncommitted changes, determines whether they belong to the current task, and blocks finish-work if current-task code isn’t committed yet.
Task archiving + journal recording: Archives the active (and optionally additional) completed tasks, then records a session journal via add_session.py.

Quick Start

Finish the session by running the Trellis finish-work command for the current 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 completed tasks and record a session journal after finishing a coding workflow?▼

To archive completed tasks and record a session journal, you can run the finish-work command which inspects active tasks, archives finished ones via auto-commit, and writes a session journal using work-commit hashes.

How do I prevent uncommitted git changes from being mistakenly left out during a session wrap-up?▼

During session wrap-up, dirty-path classification guardrails detect uncommitted changes, determine if they belong to the current task, and block the finish-work process if current-task code remains uncommitted.

What is the best way to ensure quality gates have passed before archiving tasks in a git workflow?▼

The best way to ensure quality gates pass before archiving tasks is to run a deterministic cleanup process that inspects active tasks and git status, verifying all current-task changes are properly committed before archival.

Does the session wrap-up process work with uncommitted changes from other terminals?▼

Yes, the session wrap-up process classifies dirty git paths to determine whether uncommitted changes belong to the current task, preventing unrelated work from other terminals from being incorrectly mixed into the archival.

When do I need to use a deterministic cleanup process for end-of-session task archiving?▼

You need a deterministic cleanup process for end-of-session task archiving when you want to safely close out a coding session, verify quality gates, and record what happened without incorrectly committing or mixing unrelated work.

Why does finish-work block task archiving when current-task code is not committed?▼

Finish-work blocks task archiving when current-task code is uncommitted because it needs to ensure quality gates have passed and current-task changes are safely committed, preventing accidental loss of work during the session journal recording.