‹ 首页

triage

@darkroomengineering · 收录于 昨天 · 上游提交 昨天

First-pass review of a client or unfamiliar repo — pull latest, sweep for glaring issues, report ranked findings. READ-ONLY on external repos. Triggers "triage this repo", "point out glaring issues", "review the codebase and tell me what needs fixing", "first pass on this client repo".

场景代码评审熟悉新项目质量检查

适合你，如果你需要迅速了解一个不熟悉的代码库或客户项目，找出需要修复的地方。

/ 下载安装
https://github.com/darkroomengineering/cc-settings/tree/main/skills/triage ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add darkroomengineering/cc-settings/triage
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- darkroomengineering/cc-settings/triage
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify darkroomengineering/cc-settings/triage
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
40GitHub stars
~352上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 fa04efc · 表述以原文为准
它做什么

装上后，Claude会拉取仓库最新代码，检查结构、依赖、代码规范、性能、可访问性和安全问题，生成排序报告（关键/应修复/外观），并标识哪些可直接修复、哪些需客户沟通。

什么时候触发

当你提出“triage this repo”、“point out glaring issues”、“review the codebase”等要求时触发。

装好后可以这样说
执行首次审查，生成排序报告
指出代码中的明显问题
技能原文 SKILL.md作者撰写 · MIT · fa04efc

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
  1. git checkout main 2>/dev/null; git pull — triage latest, note the default branch.
  2. Fan out explore agents in ONE message:
  3. (a) structure + dependency freshness
  4. (b) TypeScript/lint/config hygiene
  5. (c) obvious perf and a11y issues on key pages
  6. (d) security smells (exposed env, secrets in history, unpinned actions)
  7. Rank findings: Critical / Should-fix / Cosmetic. Each with file:line and a one-line fix sketch. Max 15 findings — this is a triage, not an audit; recommend /nuclear-review if depth is warranted.
  8. 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, /nuclear-review, or nothing
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…