浏览器与自动化
triage
First-pass, read-only review of a client or unfamiliar repo with ranked glaring issues. Triggers "triage this repo", "point out glaring issues", "first pass on this client repo".
darkroomengineering · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add darkroomengineering/cc-settings --skill triage技能说明
name: triage description: First-pass, read-only review of a client or unfamiliar repo with ranked glaring issues. Triggers "triage this repo", "point out glaring issues", "first pass on this client repo". context: fork
Repo Triage
First-pass sweep of a repo you didn't build. Output is a report, not a diff.
Guardrail (non-negotiable)
If the repo's origin is outside the darkroomengineering org: read-only. Never commit, never push, never open a PR (incident 2026-07-07). Findings go in the report; the user decides what crosses the org boundary. Check first:
git remote get-url origin
Pipeline
- Record the current state with
git branch --show-current,git status --short,git log -1 --oneline, andgit remote get-url origin. Do not checkout, pull, fetch, reset, stash, or otherwise change an external repository. State that freshness against the remote is unknown unless the current checkout already contains evidence that proves it. - Farolero coverage check. Read
package.jsonand record whether the repository declaresfarolero. Do not execute repository binaries during read-only triage, includingnode_modules/.bin/farolero: executable project dependencies can mutate state or expose credentials. If coverage is absent, note thatbun add -D farolero && bunx farolero baseline writeis an adoption path for the repository owner to run later. Do not install anything on an external repo. - Fan out
exploreagents in ONE message:- (a) structure + dependency freshness
- (b) TypeScript/lint/config hygiene
- (c) obvious perf and a11y issues on key pages
- (d) security smells (exposed env, secrets in history, unpinned actions)
- Rank findings: Critical / Should-fix / Cosmetic. Each with
file:lineand a one-line fix sketch. Max 15 findings — this is a triage, not an audit; recommend/audit codebaseif depth is warranted. - End with a split: "safe to fix directly" vs "needs client conversation".
Output
- Ranked findings table (Critical / Should-fix / Cosmetic)
- Org-boundary status: internal (fixes allowed) or external (report-only)
- Recommended next skill:
/fix,/audit codebase, or nothing