trellis-finish-work

To archive an active task and record session progress without committing, use a workflow that checks for a clean working tree, moves the active task to an archive, and logs a journal entry. This preserves context for future review.

A session journal helps wrap up a git coding workflow by summarizing changes, decisions, and next steps. This recording mechanism ensures continuity and a clean handoff when final commits are reserved for a later phase.

No, you cannot use this finish-work automation to commit changes. The process explicitly prohibits in-skill commits and requires a clean working tree before archiving the active task and recording the journal.

The best way to preserve context when deferring git commits is to finalize the session by archiving the active task and recording a developer journal. This enforces safety checks and retains decisions for future review.

The finish-work process requires a clean working tree before archiving tasks to prevent data loss and ensure uncommitted changes are handled separately. This safety check enforces a stable state before finalizing the session.