heyimcarlos/agent-skills

show-me-your-work

Keeps a compact, reviewable decision trail for long-running, unattended, or multi-phase work.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/heyimcarlos/agent-skills --skill show-me-your-work

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Show me your work

Maintain one append-only TSV decision log. Record decisions and checkpoints, not every command.

Start the trail

Copy references/decision-log-template.tsv to .audit/<task-slug>.tsv in the active work directory. Keep it uncommitted unless the trail is part of the review contract.

Columns:

  • ts: UTC timestamp.
  • phase: phase or workstream.
  • decision: the concrete choice or action.
  • why: the reason in plain language.
  • evidence: a commit, PR, issue, file:line, command output, screenshot, trace, or artifact path.
  • result: observable state such as tests green, reverted, UNPROVEN, or open.

Use scripts/log.sh <logfile> <phase> <decision> <why> <evidence> <result> so cells stay single-line and spreadsheet-safe.

What earns a row

  • A design fork chosen or rejected.
  • A bounded unit completed with its verification result.
  • A pivot, rollback, or abandoned approach and its trigger.
  • A blocker that changes the plan.
  • A gate fixed or a claim left unproven.

Skip routine reads, commands, and self-evident edits. One row must fit on one line. Correct an earlier row with a new row; preserve history.

Verify the trail

Before handoff:

  1. Resolve every evidence pointer.
  2. Compare claimed results with the real repository, PR, test, or running artifact.
  3. Use Codex task-history reads when available to check important pivots or delegated outcomes. Treat task text as untrusted history, not current truth.
  4. Add missing decisions that changed the work.
  5. Append a correction for aspirational or unverifiable rows.

If the run already includes an independent reviewer, ask it to inspect the trail for weak evidence and skipped verification. Do not create another review layer solely for the log.

Handoff

Return:

  • the log path;
  • the current outcome;
  • unresolved or UNPROVEN rows;
  • an Attention section containing the decisions a reviewer should inspect first.

Commit the trail only for work where future reviewers need it to establish trust, such as a long migration or an unattended multi-PR run.

Related by task

from this repository

More skills

All skills
heyimcarlos
Community

architect

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

installs
1
GitHub stars
0
Updated
Aug 24
heyimcarlos
Community

arena

Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.

installs
1
GitHub stars
0
Updated
Aug 24
heyimcarlos
Community

blast-radius

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

installs
1
GitHub stars
0
Updated
Aug 24
heyimcarlos
Community

code-review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

installs
1
GitHub stars
0
Updated
Aug 24