feat(hooks-post-tool-linter): PowerShell (?i) flag validation + §A-2 P-1/P-2 ledger (順位 7 / §A-2 P-3)

[aloekun]

Summary

• §A-2 Phase 5 dogfood P-3 (順位 7) — PR feat(lint): add PowerShell + Markdown anchor rules to ADR-007 layer (Bundle 1) #91 で発覚した PowerShell case-insensitive regex の構造的落とし穴 (Catch {} / -erroraction silentlycontinue 等を見逃す) を機械強制で再発防止
• find_powershell_rules_missing_case_insensitive_flag() 関数 + 起動時 warn (本番運用層) + 8 unit/integration test (CI 検出層) の 2 層構成
• ~/.claude/rules/common/code-review.md に case-insensitive lint rule 規約を追記 (経緯参照可能化)
• §A-2 ledger に P-1 (PR feat(cli-pr-monitor): 順位 85+86 verdict guard + matrix tests (Bundle g-1 / §A-2 P-1) #125) / P-2 (PR feat(hooks-post-tool-linter): no-time-field-strict-greater rule (順位 47 / §A-2 P-2) #126) dogfood 結果 を記録

Changes

src/hooks-post-tool-linter/src/main.rs

新関数 find_powershell_rules_missing_case_insensitive_flag(rules: &[CustomRule]) -> Vec<String>:

fn find_powershell_rules_missing_case_insensitive_flag(rules: &[CustomRule]) -> Vec<String> {
    rules.iter()
        .filter(|r| r.extensions.iter().any(|e| e.eq_ignore_ascii_case("ps1")))
        .filter(|r| !r.pattern.contains("(?i)"))
        .map(|r| r.id.clone())
        .collect()
}

• load_custom_rules() から呼出し → 起動時 stderr に warn 出力 (本番運用層)
• 8 tests 追加 (7 unit + 1 deployed-config integration):
  • flags_rule_without_case_insensitive_flag
  • passes_rule_with_case_insensitive_flag
  • ignores_non_ps1_rules
  • handles_mixed_extension_list
  • treats_extension_case_insensitively
  • returns_multiple_violators
  • deployed_custom_rules_pass_powershell_case_insensitive_validation (CARGO_MANIFEST_DIR から .claude/custom-lint-rules.toml を直読、全 rule 検証)

.claude/custom-lint-rules.toml

• 既存 no-ephemeral-todo-reference rule の pattern に (?i) 追加 (docs/todo[0-9]*\.md → (?i)docs/todo[0-9]*\.md)
  • 副次効果: Windows file path の大文字小文字混在 (Docs/Todo3.md 等) 対応
  • 必要性: extensions に ps1 を含むため deployed validation を pass させる

~/.claude/rules/common/code-review.md

### Custom lint rule patterns セクション新設:

• 必須: (?i) フラグを case-insensitive 言語 rule に付与
• テスト: 小文字 / 大文字 / 混在ケースを最低 1 ずつ検証
• machine-enforce: 起動時 warn + cargo test の自動チェックを実装
• 由来として PR feat(lint): add PowerShell + Markdown anchor rules to ADR-007 layer (Bundle 1) #91 の commit a15b263 + 順位 7 機械強制を inline cite

docs/local-llm-offload-analysis.md (§A-2 計測ログ)

P-0 / P-1 / P-2 の dogfood 結果を ___ placeholder から実数値に更新:

P-N	PR	findings	classifier 起動	agreement	latency	fallback
P-0	#123	(smoke test)	1/1 ✅	妥当	—	—
P-1	#125	0 (CR APPROVE no comments)	❌ 未起動	N/A	N/A	N/A
P-2	#126	1 (CR Nitpick, review body 内)	手動 synthetic finding 経由	1/1 (100%)	6.4s/件 (>5s 目標)	1/1 (length contract 違反)

判明した system gap (P-2): check-ci-coderabbit が CR review body の <details> block 内 Nitpick を抽出しない → post-pr-monitor の input data 経路に欠落 → classifier が空 findings を見て enrich_with_classifier をスキップ。今後の P-N で同型再発する可能性高、follow-up task 候補。

docs/todo.md / docs/todo3.md

• 順位 7 row + 詳細エントリを削除 (memory: feedback_todo_no_history 完了タスクは仕組み反映後削除)
• 別 commit (docs(todo): 順位 7 ... 完了に伴い削除) で分離

グローバル設定変更ログ (§10.5 規約)

PR #123 で導入した backup 規約に従い snapshot を取得:

__backup-claude-config/20260507-234953/
├── CLAUDE.md
├── agents/
├── rules/
├── settings.json
└── skills/

変更箇所: ~/.claude/rules/common/code-review.md に ### Custom lint rule patterns セクション追加 (約 20 行)。

Test plan

• cargo test -p hooks-post-tool-linter powershell — 7/7 pass
• cargo test -p hooks-post-tool-linter deployed_custom_rules — 1/1 pass (deployed config 全 rule バリデーション)
• cargo test -p hooks-post-tool-linter — 82/82 pass、regression なし
• pre-push-review APPROVE (1 iter / 5m 4s)
• release build + deploy (.claude/hooks-post-tool-linter.exe)
• __backup-claude-config/<ts>/ snapshot 確認
• (post-merge) classifier 起動確認 + §A-2 P-3 計測ログ記録

関連

• 順位 7 — 旧 docs/todo3.md 詳細エントリ (本 PR で削除)
• §A-2 P-3 — docs/local-llm-offload-analysis.md
• ADR-007 — custom lint rule の正規表現/AST 層線引き
• PR feat(lint): add PowerShell + Markdown anchor rules to ADR-007 layer (Bundle 1) #91 — 元の case-insensitive missing finding (commit a15b263)

[coderabbitai]

Warning

Rate limit exceeded

@aloekun has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 27 minutes and 43 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 05c3f089-31e1-4a21-8d5f-ed349d3a78c2

📥 Commits

Reviewing files that changed from the base of the PR and between b677b9d and 87e8d3d.

📒 Files selected for processing (6)

• .claude/custom-lint-rules.toml
• .markdownlint-cli2.jsonc
• docs/local-llm-offload-analysis.md
• docs/todo.md
• docs/todo3.md
• src/hooks-post-tool-linter/src/main.rs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}