Skip to content
Development
Skill

/show-me-your-work

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Explicit overlay: use for /show-me-your-work or a user

BOOST
From plugin
khanelinix
34750 skills10 agents6 commands
Install
$ npx -y skills add khaneliman/khanelinix --skill show-me-your-work --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/show-me-your-work

Context preview

The summary Claude sees to decide when to auto-load this skill.

Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Explicit overlay: use for /show-me-your-work or a user

SKILL.md

show-me-your-work.SKILL.md
name: show-me-your-work
description: "Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Explicit overlay: use for /show-me-your-work or a user request for a decision trail, not merely because work is long or multi-phase."
metadata:
  disable-model-selection: "true"

Show Me Your Work

Maintain a reviewable decision trail for unattended, multi-phase, or high-risk runs. Record what was decided, why, and on what evidence so reviewers can inspect decisions without parsing entire transcripts.

Log Format

A single TSV file with one row per decision point or checkpoint:

  • **ts**: ISO 8601 timestamp.
  • **phase**: Active workstream or phase name.
  • **decision**: One-line summary of what was chosen or executed.
  • **why**: Direct reason explaining the choice or tradeoff.
  • **evidence**: File path, commit SHA, PR number, test output, or artifact path.
  • **result**: Outcome state (`tests green`, `reverted`, `verified`, `open`).

Header template: [decision-log-template.tsv](references/decision-log-template.tsv).

Usage

Log rows using [scripts/log.sh](scripts/log.sh):

scripts/log.sh <logfile> <phase> <decision> <why> <evidence> <result>

Helper automatically stamps ISO timestamps, creates headers, escapes spreadsheet formula triggers, and strips raw control characters.

Guidelines

  • **Granularity**: Log forks, checkpoints, pivots, reverts, and verification

gates. Skip trivial edits.

  • **Append-only**: Superseded decisions get a new row; never overwrite prior

history.

  • **Location**: Keep local at `decisions.tsv` or `.audit/<task-slug>.tsv`.

Commit only when a reviewer requires the persistent audit trail.

  • **Audit**: Verify log entries against actual transcript actions before

presenting completion.

Read more
Ships withkhanelinix

Run packages directly with: Or install from the packages output. For example:

Get the whole plugin

Other skills on khanelinix.