菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/coreycoto/git-slop --skill run-report命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Integrate git-slop into a consumer repository through durable plugin source metadata, local configuration and wrapper conventions, and the advisory GitHub Action contract. Use when a user wants repository or CI adoption; use install-update instead when the outcome is only a native CLI installation.
Review existing git-slop report and health artifacts, explain detector and overlay evidence, and optionally turn one explicitly selected finding into a bounded maintenance proposal. Use when a user asks what results mean, which findings are actionable, or wants a plan from a reviewed finding; do not use merely to generate a fresh report.
Install, update, and verify the native git-slop CLI through Cargo, Homebrew, Scoop, or a checksummed release archive. Use when a machine needs a usable binary on PATH or an installed binary's version and source revision must be proven; repository configuration and GitHub Action adoption belong to the adopt-repo skill.
基于 SOC 职业分类
正在显示 SKILL.md
| 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. |
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.
git-slop findgit-slop healthgit-slop health --report <report.json>git-slop health --format jsongit-slop health --format github --max-annotations 10git-slop compare --base <old-report.json> --head <new-report.json>git-slop sarif --report <report.json> --output <path.sarif>git-slop checkDo 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.