trellis-finish-work

To archive completed tasks and record a developer journal after a coding session, use this Skill to survey active tasks, classify dirty paths, and orchestrate archival without performing commits.

The best way to clean up task state before handing off a Git repository is to verify repository cleanliness, distinguish current-task work from parallel work, and finalize session readiness with an auditable history.

No, the session journaling process does not automatically commit your changes when finishing work. It archives tasks and records progress, leaving commits for a later workflow phase.

No, you cannot use this task archiving workflow without Trellis scripts and a Python environment. It requires access to the project's Trellis scripts and uses Python to query context and classify changes.

Dirty path classification distinguishes current task work from other parallel work by querying project context through Python to sanity check dirty paths and categorize changes before archiving.

You should record session progress instead of just committing code to maintain a clean working state and ensure traceable context for handoffs and reviews through an auditable history.