skills/scouting-anomalies/SKILL.md
File-by-file read-through diagnostic to surface anomalies that fixed checklists miss. Use when: 通読, 違和感, 読み通し, 気になるとこ, read-through, anomaly scout, file-by-file review. Do NOT use for full audit (use /audit), PR screening (use /preview), or readability review (use reviewing-readability).
npx skillsauth add thkt/dotclaude scouting-anomaliesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read-through diagnostic. Staging行き、audit直結しない。
| Step | Action |
| ---- | ----------------------------------------------------------------------------- |
| 1 | 対象ファイルを 1 つずつ通読 (Read, ±20 lines) |
| 2 | 違和感候補を文字化 (1 行要約 + file:line) |
| 3 | Filter 適用 (下表) |
| 4 | 該当 reviewer の ID prefix 配列 + 該当 Category を分類 |
| 5 | staging 追記 ($HOME/.claude/workspace/scout/staging.md。無ければ mkdir -p) |
Yes/YesのみSTAGE、それ以外SKIP。
| Filter | Question | | --------------- | --------------------------------------------------------------- | | Senior Engineer | Would a senior engineer request a change? | | Harm | Concrete trigger for bug/data loss/security/maintenance burden? |
正本: ../../templates/scout/read-through-staging.md
| Field | Value |
| --------------------- | --------------------------------------------------------------------------------------- |
| severity | critical / high / medium / low |
| evidence | file:line + observation |
| reasoning | concrete language |
| existing-reviewer-fit | ID prefix 配列 (例: [CQ, PQ])。該当なしは [] |
| category-in-reviewer | 該当 reviewer の Category (例: PQ の clarity、CQ の readability)。該当なしは none |
ID prefixとCategoryは ../../templates/audit/finding-schema.md のRegistryと各reviewer定義を参照。Language Constraintsも準拠。
tools
Internal helper for /think Step 11. Renders SOW.md + Spec.md as an integrated Astro view and returns a dev server URL.
development
Extract repository spec while detecting bugs, spec gaps, and consistency drift via dual-purpose documentation. OUTCOME.md-axis question-driven exploration with ephemeral output. Do NOT use for code review (use /audit or /polish), feature implementation (use /code), planning only (use /think), or single-bug fix (use /fix).
development
Discover undocumented design decisions and challenge each candidate via critic-design before promotion. Rank by impact and reversibility, produce ADR promotion candidates. Treat each candidate as a position arguing for ADR status, not a fact to be filed. Pairs with audit-adr-drift, which scans existing ADRs for drift against code.
development
Scan ADR Decision sections against current code and report drift with modification direction and priority. Do NOT use for repos without ADRs (use audit-adr-gaps instead).