chore: focus coderabbit on meaningful suggestions

[transphorm]

Summary

• guide CodeRabbit to ignore low priority issues and concentrate on more impactful feedback

Testing

• yarn workspaces foreach -p -v --topological-dev --since=HEAD run nice --if-present
• yarn lint
• yarn build
• yarn workspace @selfxyz/contracts build (fails: Invalid account config)
• yarn types
• yarn test (fails: workspaces @selfxyz/circuits and @selfxyz/contracts)

---

https://chatgpt.com/codex/tasks/task_b_689e617dddbc832d8b50ecfb18fbebef

Summary by CodeRabbit

• Chores
  • Refined automated review settings to highlight only medium-or-higher priority issues.
  • Enabled automatic reviews for changes targeting the main and dev branches.
  • Expanded review coverage to shared utilities, SDKs, and related components for broader quality checks.
  • No user-facing behavior changes; this improves internal review consistency and coverage without affecting app functionality.

[coderabbitai]

Warning

.coderabbit.yaml has a parsing error

The CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file.

💥 Parsing errors (1)

duplicated mapping key in ".coderabbit.yaml" (15:3)

 12 |   high_level_summary: true
 13 |   poem: true
 14 |   review_status: true
 15 |   review_status: true
--------^
 16 |   auto_review:
 17 |   auto_review:

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

Updated .coderabbit.yaml to refine reviewer persona text, set a global review priority threshold to medium, specify auto-review base branches (main, dev), and expand path-specific review instructions to cover Noir circuits, shared common code, SDK packages, and an alpha mobile SDK. Existing Android/iOS and test scopes remain unchanged.

Changes

Cohort / File(s)	Summary of Changes
CodeRabbit config updates ./.coderabbit.yaml	Reworded tone_instructions; added reviews.priority_threshold: medium; added auto_review.base_branches: ["main","dev"]; introduced path_instructions for noir/**/*.nr, common/src/**/*.{ts,tsx,js,jsx}, sdk/**/*.{ts,tsx,js,jsx}, and packages/mobile-sdk-alpha/**/*.{ts,tsx,js,jsx}; retained Android/iOS and test-review sections.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• configure coderabbitai #670 — Similar .coderabbit.yaml updates adjusting auto-review branches and adding path-specific rules (including Noir and RN/TS paths).

Poem

Config whispers to the bots at night,
Medium storms, no trivial light,
Main and dev now cue the scan,
Noir and SDK join the plan.
Common threads stitch reviews tight—
One YAML tune, and all’s in sight.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/update-.coderabbit.yaml-for-priorities

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[transphorm]

@coderabbitai full review

[coderabbitai]

✅ Actions performed

Full review triggered.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 0cf1bc8 and e887685.

📒 Files selected for processing (1)

• .coderabbit.yaml (2 hunks)

🔇 Additional comments (4)

.coderabbit.yaml (4)

5-7: Persona and severity focus look good

Clear reviewer scope and severity gating. The content length stays within the tone_instructions max limit.

---

62-69: Shared utilities path instructions are solid

Good emphasis on reusability, safety, and docs for common/src. This should improve signal/noise on shared modules.

---

70-82: SDK and alpha mobile SDK coverage looks appropriate

Clear review focus areas for SDKs, including API stability and cross-env compatibility. Calling out experimental TODOs in the alpha package is helpful for triage.

---

48-54: Action required — .coderabbit.yaml 'noir//*.nr' glob matches no files**

I searched the repo for noir/**/*.nr and found 0 matches; the review instructions in .coderabbit.yaml will not be applied as written.

• File to update:
  • .coderabbit.yaml — lines ~48–54

    - path: "noir/**/*.nr"
      instructions: |
        Review Noir circuits for:
        - Constraint and witness correctness
        - Efficient proof generation and verification
        - Soundness and security assumptions
        - Clear separation of public and private inputs
    

Suggested actions (pick one):

• Update the glob to the actual location of your Noir files (e.g., "/*.nr" or "zk/noir//*.nr").
• If circuits will be added later, add a comment or note to avoid confusion.
• Remove the block if Noir review instructions are not needed.

Please confirm which option you want.