skills.rest
imbingox
imbingoxCOMMUNITY
Explore all skills by this author →
GitHub

trellis-finish-work

Archive completed Trellis tasks and record a session progress journal.

Updated Mar 25, 2026
Search Tags:#journal#session-management#dev-workflow#trellis#finish-work#git-archiving
One-click install
npx skills add https://github.com/imbingox/acex --skill trellis-finish-work-imbingox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-finish-work
Source: https://github.com/imbingox/acex/tree/main/.agents/skills/trellis-finish-work
Command: npx skills add https://github.com/imbingox/acex --skill trellis-finish-work-imbingox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wrap up the current Trellis coding session by auditing active tasks, archiving completed work, and recording progress to the developer journal.

Core Features & Use Cases

  • Survey and verify the current session state (active tasks, recent commits) to determine what should be archived.
  • Distinguish between current-task changes and parallel work, preventing mixed commits and guiding focused archiving.
  • Archive tasks with automated commits and maintain a clean, traceable Git history.
  • Record the session journal to preserve context for future review and handoff.

Quick Start

Run the Trellis finish-work command to archive the current task 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 coding tasks and record a session journal at the end of a work session?▼

To archive completed coding tasks, the session workflow surveys active tasks, differentiates current work from parallel changes, performs automated Git commits, and records a structured progress journal to preserve context.

How does session archiving handle parallel changes separately from the current task scope?▼

Session archiving distinguishes current-task changes from parallel work by surveying the session state and validating dirty files, preventing mixed commits to maintain a clean and traceable Git history.

What is the best way to maintain a clean Git history when wrapping up multiple active tasks?▼

The best way to maintain a clean Git history when wrapping up active tasks is to use an automated archiving workflow that differentiates current-task changes from parallel work and generates focused, structured commits.

Do I need to manually validate dirty files before archiving a coding session?▼

You do not need to manually validate dirty files before archiving a coding session, because the finish-work workflow enforces safe guardrails that automatically survey session state and validate changes before performing automated Git commits.

Why should I record a developer journal after finishing a Git work session?▼

Recording a developer journal after finishing a work session preserves context for future review and handoff, ensuring the rationale behind completed tasks and structured commits remains traceable.

Related Skills

Explore More Software Engineering Skills→
hksloverhkslover
47

trellis-start

Load Trellis project context and workflow state to initialize development sessions.

Community
Intermediate
All-The-VibesAll-The-Vibes
50

land

Commit changes, push to the remote, and open a pull request for handoff.

Official
Advanced
RebornQRebornQ
52

trellis-finish-work

Archive active Trellis tasks and update the developer journal.

Community
Advanced
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic