trellis-finish-work

You can wrap up a coding session by running a finish-work command that archives active tasks and saves a developer journal. It validates your repository for a clean working tree before archiving, ensuring safe handoffs and traceable session history.

The best way to ensure a clean working tree before task archiving is using an automated session wrap-up workflow. It validates your repository state as a strict safeguard, refusing to archive tasks or record journals until your working tree is clean.

No, the session wrap-up process does not perform Git commits during task archiving. It strictly records a session journal that links work to existing commits and future references, leaving the actual code commits to be handled separately.

You need a developer journal for end-of-session workflows to maintain traceable session history. It records completed work and links it to commits, providing an auditable trail and clear context for future references without altering your codebase.

Yes, you can archive multiple completed tasks at once during a coding session wrap-up. The workflow cleans up completed-but-unarchived work alongside your active task, ensuring all finished items are safely archived in a single auditable step.

If your repository has uncommitted changes during task archiving, the workflow enforces safeguards by validating the repository state. It requires a clean working tree before proceeding, preventing unsafe handoffs and ensuring all work is properly tracked.