Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
日本語の概要は準備中です。原文の説明を表示しています。
Git change frequency hotspot analysis — find the most-changed files in your codebase
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Wave: CROSS_WAVE Execution: Inline (no agent — Claude executes git commands directly) Inspiration: Adam Tornhill's "Your Code as a Crime Scene"
Analyze git change frequency to identify the most-changed files in a codebase. Pure git churn — no complexity metrics. Use as a pre-filter to scope analysis or a post-filter to prioritize existing findings.
Run git log --name-only over the configured time period, count commits per file, rank by frequency.
Show the most-changed files in the repo. Output is inline only — no files persisted.
/nw-hotspot
/nw-hotspot --top=20
/nw-hotspot --since=12m
Steps:
git log --since={since} --format=format: --name-only | sort | uniq -c | sort -rntest -f)git log -1 --format="%ar" -- {file} Rank │ Commits │ Last Changed │ File
──────┼─────────┼──────────────┼─────────────────────────
1 │ 87 │ 2 days ago │ src/services/payment.ts
2 │ 64 │ 1 week ago │ src/api/controllers/user.ts
3 │ 51 │ 3 days ago │ src/models/order.ts
Defaults: --top: 15, --since: 6 months
Overlay churn data on an existing analysis report to prioritize findings.
/nw-hotspot --rank code-smell-detector-report.md
Steps:
Deep-dive into a single file's change history.
/nw-hotspot --detail src/services/payment.ts
Steps:
/nw-hotspot --top=10 --json
Output: [{"path": "src/services/payment.ts", "commits": 87, "last_changed": "2 days ago"}, ...]
| Flag | Default | Description |
|---|---|---|
--top | 15 | Number of files to show |
--since | 6m | Time period (e.g., 3m, 12m, 2024-01-01) |
--json | false | Output as JSON array |
--rank | - | Path to existing report to re-rank by churn |
--detail | - | Path to single file for deep-dive |
--follow; keeps it simple and fast)Run /nw-hotspot --top=10 --json first, then pass the file list to:
Run /nw-hotspot --rank {report.md} after any analysis to prioritize by churn.
/nw-refactor — identify which files to refactor first/nw-review — focus review effort on high-churn areas/nw-root-why — check if the problematic area is a known hotspotUsage Context: Inline utility, composable with any analysis skill Handoff To: Invoking context (no sequential handoff)
/nw-hotspot
/nw-hotspot --top=10 --json
/nw-hotspot --rank code-refactoring-report.md
/nw-hotspot --detail src/services/payment.ts
No persistent files. Output is displayed inline. JSON mode outputs a JSON array for composition with other tools.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
日本語の概要は準備中です。原文の説明を表示しています。
Review dimensions for validating agent quality - template compliance, safety, testing, and priority validation
日本語の概要は準備中です。原文の説明を表示しています。
Review dimensions for acceptance test quality - happy path bias, GWT compliance, business language purity, coverage completeness, walking skeleton user-centricity, priority validation, observable behavior assertions, traceability coverage, and walking skeleton boundary proof
日本語の概要は準備中です。原文の説明を表示しています。
Detailed 5-phase workflow for creating agents - from requirements analysis through validation and iterative refinement
日本語の概要は準備中です。原文の説明を表示しています。
5-layer testing approach for agent validation including adversarial testing, security validation, and prompt injection resistance
日本語の概要は準備中です。原文の説明を表示しています。
Architectural style selection decision matrices, trade-off analysis, structural enforcement rules, and combination patterns. Load when choosing or evaluating architecture styles.
日本語の概要は準備中です。原文の説明を表示しています。