agentleFS
wuwei-crgwuwei-crg/LXB-Framework/.agents/skills/trellis-finish-work/SKILL.md

trellis-finish-work

Skill301 starsChanged 6 months agoMITView on GitHub

Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal. Use when done coding and ready to end the session.

16 other projects use a version of this, 13 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use trellis-channel, trellis-session-insight and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • wayfarer35Skill

    trellis-channel

    Use Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.

    Also in 14 projects that use this

  • wayfarer35Skill

    trellis-session-insight

    Reach into past AI conversation history through the `trellis mem` CLI. Use whenever the user asks 'how did we solve X last time', 'have we discussed this before', 'what was the decision on X', 'remind me what we did in this task', '上次怎么解的', '之前讨论过吗', '想起一段对话', or when starting a brainstorm that overlaps prior work, debugging a familiar bug, continuing a task across sessions, or doing a finish-work review. Returns raw past dialogue; decide for the moment whether to update spec, append to task notes, quote inline in the answer, or just internalize.

    Also in 14 projects that use this

  • +1 more from wayfarer35

The file

We split this skill into the rules it gives an agent

3 rules. 2 are common, 0 are distinctive, and 1 is very specific to this project.

  • 2

    Common

    Most of the 13 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Do NOT run git commit here.

    line 45
  2. Common:

    If there is no active task and the user did not confirm any cleanup archives, skip this step.

    line 58
  3. Very specific:

    Use the work-commit hashes produced in Phase 3.4 (visible in Step 1's Recent commits list, or via git log --oneline) for --commit.

    line 69

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Finish Work

Wrap up the current session: archive the active task (and any other completed-but-unarchived tasks the user wants to clean up) and record the session journal. Code commits are NOT done here — those happen in workflow Phase 3.4 before you invoke this command.

Step 1: Survey current state

python ./.trellis/scripts/get_context.py --mode record

This prints:

  • My active tasks — review whether any besides the current one are actually done (code merged, AC met) and should be archived this round.
  • Git status — quick visual on what's dirty.
  • Recent commits — you'll need their hashes in Step 4 for --commit.

If --mode record surfaces other completed tasks not tied to the current session, surface them to the user with a one-shot confirmation: "These N tasks look done — archive them too in this round? [y/N]". Default is no; the current active task is always archived in Step 3 regardless.

Step 2: Sanity check — classify dirty paths

Run:

git status --porcelain

Filter out paths under .trellis/workspace/ and .trellis/tasks/ — those are managed by add_session.py and task.py archive auto-commits and will appear dirty as part of this skill's own work.

For each remaining dirty path, decide whether it belongs to the current task or to other parallel work (e.g., another terminal window editing the same repo). Heuristics:

  • Paths referenced in the current task's prd.md / implement.jsonl / check.jsonl → current task
  • Paths in code areas matching the task's stated scope, or that you remember editing this session → current task
  • Paths in unrelated areas you have no recollection of touching this session → other parallel work

Then route:

  • Any remaining path looks like current-task work — bail out with:

    "Working tree has uncommitted code changes from this task: <list>. Return to workflow Phase 3.4 to commit them before running ``finish-work (Trellis command)."

    Do NOT run git commit here. Do NOT prompt the user to commit. The user goes back to Phase 3.4 and the AI drives the batched commit there.

  • All remaining paths look unrelated (other parallel-window work) — report them once and continue to Step 3:

    "FYI, dirty files outside this task's scope — leaving them for the other window: <list>."

  • Genuinely unsure — ask the user once: "Are <list> this task's work I forgot to commit, or another window's? (commit / ignore)" — then route per their answer.

Step 3: Archive task(s)

python ./.trellis/scripts/task.py archive <task-name>

At minimum: the current active task (if any). Plus any extra tasks the user confirmed in Step 1. Each archive produces a chore(task): archive ... commit via the script's auto-commit.

If there is no active task and the user did not confirm any cleanup archives, skip this step.

Step 4: Record session journal

python ./.trellis/scripts/add_session.py \
  --title "Session Title" \
  --commit "hash1,hash2" \
  --summary "Brief summary"

Use the work-commit hashes produced in Phase 3.4 (visible in Step 1's Recent commits list, or via git log --oneline) for --commit. Do not include the archive commit hashes from Step 3. This produces a chore: record journal commit.

Final git log order: <work commits from 3.4> → chore(task): archive ... (one or more) → chore: record journal.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.