trellis-finish-work

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

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-finish-work-hejiajiudeeyu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-finish-work
Source: https://github.com/hejiajiudeeyu/delegated-execution-workspace/tree/main/.agents/skills/trellis-finish-work
Command: npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-finish-work-hejiajiudeeyu

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. This Skill automates that wrap-up sequence so nothing is forgotten and the project history stays consistent. ## Core Features & Use Cases - Dirty-tree classification: Inspects git status output, separates current-task changes from unrelated parallel work, and blocks the wrap-up if uncommitted task code remains. - Task archiving: Archives the active task (plus any other completed tasks the user confirms) 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 the code in your workflow's commit phase, run this Skill to archive the task and log the session so the next session starts from a clean, documented state. ## Quick Start Ask the AI to finish the work session by archiving the current 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 wrap up a coding session in a Trellis-managed project?▼

Run the finish-work flow after committing your code: it surveys active tasks, checks the git working tree, archives completed tasks with task.py archive, and records a session journal with add_session.py including your work commit hashes.

Does finish-work commit my code changes automatically?▼

No, code commits are explicitly not done by this Skill. If uncommitted changes belonging to the current task are detected, it stops and directs you back to the commit phase of the workflow before wrapping up.

What happens if git status shows dirty files from another terminal window?▼

The Skill classifies each dirty path as current-task work or unrelated parallel work using task file references and session memory. Unrelated paths are reported once and left untouched, while ambiguous paths trigger a single confirmation question.

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. The archive commits created by task.py archive are excluded, keeping the journal focused on actual code changes.

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

Yes. When the context survey surfaces other completed-but-unarchived tasks, the Skill asks for one confirmation and archives them alongside the current active task, each producing its own chore(task): archive commit.