trellis-finish-work

Archives completed Trellis tasks and records a session journal.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/MrHan-Yd/DdShell --skill trellis-finish-work-mrhan-yd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-finish-work
Source: https://github.com/MrHan-Yd/DdShell/tree/main/.agents/skills/trellis-finish-work
Command: npx skills add https://github.com/MrHan-Yd/DdShell --skill trellis-finish-work-mrhan-yd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the graceful wrap-up of a Trellis coding session: archive completed tasks, collect context, and record the session progress for the developer journal.

Core Features & Use Cases

  • Archive active tasks and any completed-but-unarchived tasks within the session.
  • Surface and summarize dirty changes to confirm scope before archiving.
  • Record a session journal with commit references for traceability.

Quick Start

Execute finish-work to wrap up the current Trellis session, archive completed work, and record the session journal.

Frequently Asked Questions about trellis-finish-work

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

FAQPage Schema
How do I archive completed tasks and record a journal at the end of a Trellis session?

To archive Trellis session tasks and record a journal, execute the finish-work workflow which surveys your workspace state, classifies dirty paths, archives completed tasks, and documents session progress with commit references.

How do I safely handle uncommitted changes when wrapping up a coding session?

To handle uncommitted changes safely during session wrap-up, the workflow surfaces and summarizes dirty paths, classifying current-task changes versus parallel work to prevent committing unintended modifications before archiving.

What is the best way to track session progress in a developer journal?

Tracking session progress in a developer journal involves archiving active tasks and recording a session journal with explicit commit references, ensuring traceability of completed work within a shared workspace.

Can I wrap up a Trellis workspace with multiple parallel tasks tracked in a single session?

Yes, you can wrap up a Trellis workspace with parallel tasks by carefully differentiating current-task changes from parallel work, ensuring uncommitted changes are classified and handled safely before archiving completed tasks.

Why should I classify dirty paths before archiving completed tasks in my workflow?

Classifying dirty paths before archiving tasks acts as an explicit safeguard against committing unintended changes, ensuring only current-task modifications are finalized while parallel work remains safely uncommitted in the workspace.