Strict project-aware CodeRabbit review config

[vishnujayvel]

Summary

• Replaces lightweight 4-path CodeRabbit config with strict 9-path project-aware review rules
• Encodes hookwise-specific invariants: three-phase separation, fail-open guarantee, first-match-wins guards, stateless feed producers, cache bus persistence, daemon PID lifecycle
• Adds severity categorization (Critical/Important/Minor) aligned with superpowers code-reviewer patterns
• New path coverage: src/core/feeds/**, src/core/status-line/**, src/cli/**, docs/**, src/core/recipes.ts

Test plan

• CodeRabbit picks up the new config on next PR
• Review comments reference project-specific invariants (not generic advice)
• Severity levels appear in CodeRabbit output

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Enabled stricter review workflow enforcement (request-changes now required) and clarified reference configuration role.

• Documentation

  • Added extensive architecture and docs guidance: guard/phase separation, validation and schema expectations, error categorization, CLI/status-line behavior, producer/cache/daemon expectations, test naming and patterns, runnable examples, and configuration validation.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Warning

Ignoring CodeRabbit configuration file changes. For security, only the configuration from the base branch is applied for open source repositories.

ℹ️ Recent review info

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9c36787 and 6aac62c.

📒 Files selected for processing (1)

• .coderabbit.yaml

---

📝 Walkthrough

Walkthrough

This PR updates the CodeRabbit configuration to enable the request_changes_workflow and replaces broad TypeScript review guidance with detailed, architecture- and path-specific review instructions (guards, context, side effects, validation, error handling, CLI/daemon/recipes/tests/docs expectations, and hookwise.yaml schema guidance).

Changes

Cohort / File(s)

Summary

CodeRabbit config \.coderabbit\.yaml

Enabled request_changes_workflow. Replaced generic TypeScript review rules with detailed per-path architecture-focused instructions (rules for src/core, src/core/feeds, src/core/status-line, src/cli, src/core/recipes.ts, src/testing, tests, hookwise.yaml, docs, etc.). Added explicit hookwise.yaml schema/validation expectations, guard semantics (three-phase: guards/context/side-effects, first-match-wins, JSON-validated guard output), error categorization, producer/cache/daemon/registry guidance, CLI/exit-code/CI requirements, recipe/docs/manifest expectations, and standardized test patterns and naming conventions.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• Strict project-aware CodeRabbit review config #1 — Makes essentially the same edits to .coderabbit.yaml and per-path architecture-focused review rules; likely a direct duplicate or closely related change.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: updating the CodeRabbit review configuration to be stricter and project-aware.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch strict-coderabbit-config

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.coderabbit.yaml:
- Around line 84-95: The .coderabbit.yaml currently applies two overlapping
rules to the same file: the explicit path entry "src/core/recipes.ts" and the
glob "src/core/*.ts" both match src/core/recipes.ts, causing duplicated/multiple
instruction sets; decide whether recipes.ts should receive both core invariants
and recipe-specific checks—if not, remove or rename the explicit entry or modify
the glob to exclude recipes.ts (e.g., change the glob or add a
negative/exclusion pattern) so only one rule applies; alternatively, if the
overlap is intentional, add a comment in .coderabbit.yaml clarifying that
"src/core/recipes.ts" should get both rule sets to avoid future confusion.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 939367b and 9c36787.

📒 Files selected for processing (6)

• .coderabbit.yaml
• docs/guide/creating-a-recipe.md
• docs/guide/getting-started.md
• docs/reference/hook-events.md
• docs/reference/migration.md
• docs/reference/tui-guide.md