trellis-finish-work

Archives completed tasks and records session journals after verifying committed work.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/gyc-12/Archipelago --skill trellis-finish-work-gyc-12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-finish-work
Source: https://github.com/gyc-12/Archipelago/tree/main/docs/trellis/skills/trellis-finish-work
Command: npx skills add https://github.com/gyc-12/Archipelago --skill trellis-finish-work-gyc-12

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 logging what was accomplished—which are easy to forget or do inconsistently. ## Core Features & Use Cases - Dirty-tree classification: Surveys uncommitted changes and distinguishes current-task work from unrelated parallel edits, blocking the wrap-up if task code is still uncommitted. - Task archiving: Archives the active task plus any other confirmed completed tasks via task.py archive, producing auto-committed chore(task): archive entries. - Session journaling: Records a session summary linked to the relevant commit hashes via 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 append a journal entry so the next session has full context. ## Quick Start Ask the AI to finish the current Trellis work session by archiving the completed task and recording a session journal with the recent commit hashes.

Frequently Asked Questions about trellis-finish-work

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

FAQPage Schema
How do I properly end a Trellis coding session?

Commit all task work in workflow Phase 3.4 first, then run the finish-work skill. It surveys active tasks, archives completed ones with task.py archive, and records a session journal via add_session.py linked to your commit hashes.

What happens if I have uncommitted changes when finishing work?

The skill classifies dirty paths from git status, excluding .trellis/workspace and .trellis/tasks. If remaining changes belong to the current task, it stops and tells you to return to Phase 3.4 to commit; unrelated changes are reported and left alone.

Does finish-work create git commits for my code?

No, code commits are never made by this skill. It only produces chore(task): archive commits and a chore: record journal commit through its scripts. Your work commits must already exist from Phase 3.4.

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

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

Which commit hashes go into the session journal?

Use the work-commit hashes produced in Phase 3.4, visible in the recent commits list or via git log. Do not include the archive commit hashes generated during task archival.