Repository navigation
chore: Claude Code自動化の導入(hooks / Convex MCP / skill / subagent) - #2
Conversation
- PostToolUse hook: .ts/.tsx編集後に tsc --noEmit で即時型チェック - permissions.deny: .env* ファイルのAIによる編集を禁止 - .mcp.json: Convex公式MCPサーバー(dev環境のデータ照会・関数実行) - /implement-phase skill: フェーズ実装の定型フロー(ブランチ→実装→検証→PR) - tenant-isolation-reviewer subagent: Convex公開関数の認可漏れ専門検査 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TXR7e4TNzw439UpX5JQTuC
|
Warning Review limit reached
Next review available in: 35 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
- hooks: jq未インストール時に黙って型チェックをスキップせず、exit 2で明示的に失敗させる - implement-phase skill: 検証フローにテスト実行(vitest)を追加 - tenant-isolation-reviewer: storageIdの世帯帰属検証を検査項目に追加 - Write(.env*)の削除提案は見送り(冗長だが無害なため防御として残す) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TXR7e4TNzw439UpX5JQTuC
概要
/claude-automation-recommender の分析結果に基づき、開発を自動化する設定一式を追加する。
追加内容
.claude/settings.json.ts/.tsx編集のたびにtsc --noEmitを実行し、型エラーを即座にAIへフィードバック.claude/settings.jsonpermissions.denyで.env*のAIによる編集を禁止(秘密鍵の誤編集防止).mcp.json.claude/skills/implement-phase//implement-phase Nでフェーズ実装の定型フロー(ブランチ→実装→検証→PR)を実行。mainへの直接コミットとPR自動マージを禁止事項として明記.claude/agents/tenant-isolation-reviewer.md検証
.claude/settings.json/.mcp.jsonはjqで構文・スキーマ検証済みマージ後の利用者側の作業
.mcp.jsonのconvexサーバーを承認するプロンプトが出るので許可する🤖 Generated with Claude Code
https://claude.ai/code/session_01TXR7e4TNzw439UpX5JQTuC