trellis-finish-work

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

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/jiozhaoyue/ST-BgLoader --skill trellis-finish-work-jiozhaoyue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-finish-work
Source: https://github.com/jiozhaoyue/ST-BgLoader/tree/main/.reasonix/skills/trellis-finish-work
Command: npx skills add https://github.com/jiozhaoyue/ST-BgLoader --skill trellis-finish-work-jiozhaoyue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a coding session cleanly requires several bookkeeping steps: confirming all work is committed, archiving finished tasks, and writing a session journal. This Skill automates that wrap-up sequence so nothing is forgotten and the project history stays consistent. ## Core Features & Use Cases - State Survey: Runs get_context.py to list active tasks, git status, and recent commits before wrapping up. - Dirty Path Classification: Inspects git status, filters out Trellis-managed paths, and routes uncommitted changes back to the commit phase or flags them as parallel work. - Task Archival & Journaling: Archives completed tasks via task.py and records a session journal with commit hashes via add_session.py. - Use Case: After finishing a feature and committing code in Phase 3.4, invoke this Skill to archive the task and log the session, producing a clean git history of work, archive, and journal commits. ## Quick Start Ask the AI to run the trellis-finish-work skill to wrap up the current session after all code changes have been committed.

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 coding session in a Trellis-managed project?▼

Run the trellis-finish-work skill after committing your code. It surveys active tasks, checks git status, archives completed tasks with task.py, and records a session journal with add_session.py including your work commit hashes.

What happens if I have uncommitted changes when finishing work?▼

The skill classifies dirty paths from git status. Paths belonging to the current task cause it to bail out and direct you back to the commit phase; unrelated paths from parallel work are reported and left untouched.

Does trellis-finish-work commit my code changes?▼

No. Code commits happen in workflow Phase 3.4 before invoking this skill. It only creates archive commits via task.py and a journal commit via add_session.py, never committing work code itself.

Can I archive multiple completed tasks in one session wrap-up?▼

Yes. The skill surfaces other completed-but-unarchived tasks and asks for one-shot confirmation. The current active task is always archived; additional tasks are archived only if you confirm.

Which commit hashes go into the session journal?▼

Only the work-commit hashes produced during the commit phase are passed to add_session.py via --commit. Archive commit hashes from the archival step are explicitly excluded from the journal entry.