| name | run-report |
| description | Generate and render git-slop reports, health output, comparisons, SARIF, and explicit checks while preserving local artifact and advisory CI conventions. Use when a user wants fresh or re-rendered detector output; use review-results to interpret findings or plan maintenance. |
Run Git Slop Reports
Use this skill when the user wants a fresh or re-rendered git-slop report.
Use review-results to interpret findings or plan bounded maintenance.
Commands
- Generate artifacts:
git-slop find
- Render the human health dashboard:
git-slop health
- Render a selected report:
git-slop health --report <report.json>
- Emit the health payload for automation:
git-slop health --format json
- Emit bounded CI annotations:
git-slop health --format github --max-annotations 10
- Compare existing reports:
git-slop compare --base <old-report.json> --head <new-report.json>
- Export SARIF locally:
git-slop sarif --report <report.json> --output <path.sarif>
- Run the gate surface:
git-slop check
Do not adopt a repository merely to inspect it. Before git-slop init, a plain
find automatically writes report.json, summary.md, and health.md under
Git-private ephemeral state; downstream commands discover that active state.
Use --persist-unadopted only when the user explicitly wants persistent
pre-adoption output. Run git-slop init only when durable .slop/ adoption is
the requested outcome.
After adoption, one successful find writes the artifacts to both
.slop/latest/ and a timestamped .slop/runs/ directory. It also writes
report.yaml when output.yaml: true.
health and the other downstream commands consume those reports. health
writes its selected rendering to stdout; it does not rewrite health.md or
rerun find. Health findings are advisory and a successful rendering exits
zero. Use check when the repository explicitly wants an enforcement gate.
Read the health command reference when selecting a
format, interpreting health evidence, or reproducing the GitHub Action flow.
Generated .slop/latest/, .slop/runs/, .slop/cache/, .slop/advice/,
Git-private first-run state, prompt packs, SARIF exports, plan JSON, and compare
JSON should stay untracked unless a repository intentionally curates examples
or fixtures outside the runtime .slop/ tree.
Upload a bounded generated artifact when review needs a durable copy. Prefer
health.md alone; add report.json only when automation needs schema-5 data.
Consumer repos may provide a wrapper such as ./scripts/git_slop.sh; prefer it
when present because it may enforce the repo's pinned install contract.
