skills.rest
tincopper
tincopperCOMMUNITY
Explore all skills by this author →
GitHub

trellis-finish-work

Archive completed Trellis tasks and write a session journal.

10|Updated Mar 21, 2026
Search Tags:#commit history#git status#trellis#session cleanup#workflow handoff#task archiving#developer journal
One-click install
npx skills add https://github.com/tincopper/neeko --skill trellis-finish-work-tincopper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-finish-work
Source: https://github.com/tincopper/neeko/tree/main/.agents/skills/trellis-finish-work
Command: npx skills add https://github.com/tincopper/neeko --skill trellis-finish-work-tincopper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill closes out a finished Trellis work session without losing track of what was done, what still needs a commit, or which archived tasks and journal entries must be recorded.

Core Features & Use Cases

  • Checks the current workspace state before ending the session.
  • Classifies dirty files so task-related changes are caught before archiving, while unrelated parallel-window work is left alone.
  • Archives completed tasks and records a session journal with the relevant commit history.
  • Use it when you have finished coding, merged the work, and want a clean handoff with a documented trail.

Quick Start

Ask the assistant to finish the current Trellis session by verifying status, archiving completed tasks, and writing 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 clean up my git status before ending a development session?▼

To clean up your git status and archive completed coding tasks, this Skill wraps up finished Trellis sessions by classifying dirty files, creating archive commits for done tasks, and leaving unrelated parallel work untouched.

What is the best way to document a developer journal with commit history during a workflow handoff?▼

Documenting a developer journal during a workflow handoff involves recording the final session state tied to prior work commits, ensuring a clean separation between current-task changes and unrelated parallel work for a documented trail.

Can I finish a Trellis work session without accidentally committing unrelated parallel work?▼

You can finish a Trellis work session safely because the Skill classifies uncommitted paths, ensuring task-related changes are caught and archived while unrelated parallel-window work is left completely alone.

How do I record the final state of a merged coding task and write a session journal?▼

Recording the final state of a merged coding task requires verifying the workspace, archiving finished tasks with their commit history, and writing a final session journal entry to close out the development session.

When should I avoid using an automated session cleanup for my git commit history?▼

You should avoid automated session cleanup if your development session is not yet finished or if you need to manually separate intertwined task-related changes from unrelated parallel-window work before archiving.

Related Skills

Explore More Software Engineering Skills→
LonelyHerbivoreLonelyHerbivore
92

trellis-finish-work

Archive completed Trellis tasks and record a session journal after verifying quality gates.

Community
Intermediate
iamcxaiamcxa
3

kc-session-resume

Restore developer session context from journal handoffs and project checkpoints.

Community
Advanced
RebornQRebornQ
52

trellis-finish-work

Archive active Trellis tasks and update the developer journal.

Community
Advanced
SilentFlowerSilentFlower

record-session

Append session summaries and commit hashes to repository journal files.

Community
Intermediate