SkillAgentSearch skills...

trellis-finish-work

Wrap up the current session: verify quality gate passed, remind user to commit, archive completed tasks, and record session progress to the developer journal

Install / Use

npx skills add fy-agent/fyagent --skill trellis-finish-work

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Category

Automation

Supported Platforms

Universal

Our assessment of trellis-finish-work

trellis-finish-work scores 87/100 on our quality scale, 1679th of 2,790 Automation skills we index.

Its SKILL.md is 3.6 KB long, split into 5 sections with 4 code examples: a solid amount of guidance for an agent.

With 1,181 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so trellis-finish-work is actively maintained.
  • Our last check on 2026-10-11 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

trellis-finish-work compared with similar skills

All 4 of these similar skills score higher than trellis-finish-work; compare them before choosing.

SkillScoreStarsUpdatedFormat
trellis-finish-work (this skill)by fy-agent871.2k55d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install trellis-finish-work?
Run npx skills add fy-agent/fyagent --skill trellis-finish-work. The install tabs above show the steps for each supported agent.
Which AI agents does trellis-finish-work work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is trellis-finish-work safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is trellis-finish-work still maintained?
The repository was last updated about 2 months ago, so trellis-finish-work is actively maintained.

name: trellis-finish-work description: "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."

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.

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryAutomation
Updated1mo ago
Forks135

Languages

Rust

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium