chore(coderabbit): add custom finishing touch recipes

[nanotaboada]

This change is 

Summary by CodeRabbit

• Chores
  • Updated CI/CD and development config to strengthen automated checks, testing, and coverage reporting.
  • Added and refined review rules and documentation-sync validations to improve code quality and docs consistency.
  • Expanded static analysis, linting, and secret/IaC scanning tool configurations; increased quality thresholds.

Note: This release contains no user-facing changes.

[coderabbitai]

Warning

Rate limit exceeded

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

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

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 781e8910-0264-43a5-a460-e9af564eb858

📥 Commits

Reviewing files that changed from the base of the PR and between ee9babc and 3c774f0.

📒 Files selected for processing (1)

• .coderabbit.yaml

Walkthrough

Updated .coderabbit.yaml with explicit path-specific review instructions (including Dockerfile, pyproject.toml, and GitHub workflows), new custom review checks (docs, error handling, idiomatic, API contract), tooling adjustments (added scanners, disabled some linters), changed pre-merge thresholds, and narrowed knowledge_base patterns.

Changes

Cohort / File(s)	Summary
Primary Config .coderabbit.yaml	Removed flags (enable_free_tier, auto_assign_reviewers, in_progress_fortune); added explicit path_instructions for Dockerfile, pyproject.toml, and .github/workflows/*.yml; added uv.lock exclusion in path_filters; adjusted pre_merge_checks threshold and toggles.
New/Updated Reviews .coderabbit.yaml	Added custom review sections: sync documentation (docstrings, README.md, copilot-instructions.md), enforce http error handling, idiomatic review, and verify api contract.
Tooling & QA .coderabbit.yaml	Expanded tools with secret scanners, IaC tools, static analysis, and file linters; disabled flake8/pylint for this project; added many tool toggles and updated unit test code_generation to run via uv with coverage reporting.
Knowledge Base & Tests .coderabbit.yaml	Narrowed knowledge_base.code_guidelines.filePatterns to only .github/copilot-instructions.md; updated unit test invocation and coverage steps to use uv and wheelhouse expectations.
Path-specific Guidance .coderabbit.yaml	Added explicit, detailed checks for Dockerfile (wheels-only, non-root user, HEALTHCHECK, pinned uv), pyproject.toml (PEP 735/uv groups, uv.lock existence/up-to-date), and GitHub workflow setup (uv setup, dev deps via uv, pytest verbosity, coverage upload).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• feat: add Copilot instructions for project context and guidelines #437: Adds/configures reviews and knowledge_base patterns specifically for .github/copilot-instructions.md.
• chore: optimize CodeRabbit configuration for Python/FastAPI project #462: Overlaps in .coderabbit.yaml edits—path_instructions, path_filters, tooling toggles, and pre_merge_checks.

🚥 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 uses the correct Conventional Commits format (chore:), is well under 80 characters (53 chars), and accurately describes the main change: adding custom review recipes/configurations to the CodeRabbit configuration file.
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 chore/coderabbit-custom-recipes

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (f1fc457) to head (3c774f0).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #509   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines          110       110           
=========================================
  Hits           110       110           

Components	Coverage Δ
Services	100.00% <ø> (ø)
Routes	100.00% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.coderabbit.yaml (1)

263-267: Consider clarifying the comment for disabled Python linters.

The comment "Disable irrelevant tools for this Python project" is slightly misleading for flake8 and pylint since they are Python tools. A more accurate comment would note that ruff (enabled above) serves as their modern replacement.

✏️ Suggested comment clarification

-    # Disable irrelevant tools for this Python project
+    # Prefer ruff over legacy Python linters (flake8, pylint)
     flake8:
       enabled: false
     pylint:
       enabled: false
+
+    # Disable tools for other languages/platforms
     shellcheck:
       enabled: false

🤖 Prompt for AI Agents

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

In @.coderabbit.yaml around lines 263 - 267, Update the YAML comment above the
flake8 and pylint settings to clarify that these tools are disabled because ruff
is enabled as the modern replacement for linting; specifically, modify the
comment that currently reads "Disable irrelevant tools for this Python project"
to mention that flake8 and pylint are intentionally disabled in favor of ruff
(which is enabled earlier in the file), and ensure the change references the
flake8 and pylint keys so reviewers understand why those entries are set to
enabled: false.

🤖 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 113-118: Make the CI instructions and workflow implementation
consistent: either update the instruction entry to match the current workflow
(change the install line to use "uv pip install --group dev" and document that
pytest is run twice, once with "-v" and once separately with "--cov"), or modify
the workflow steps to match the instructions (change the install step to "uv pip
install -e . --group dev" and replace the two pytest invocations with a single
run using both flags, e.g. "pytest -v --cov"); ensure the install command and
pytest flag usage in the instruction block exactly match the strings used in the
workflow.

---

Nitpick comments:
In @.coderabbit.yaml:
- Around line 263-267: Update the YAML comment above the flake8 and pylint
settings to clarify that these tools are disabled because ruff is enabled as the
modern replacement for linting; specifically, modify the comment that currently
reads "Disable irrelevant tools for this Python project" to mention that flake8
and pylint are intentionally disabled in favor of ruff (which is enabled earlier
in the file), and ensure the change references the flake8 and pylint keys so
reviewers understand why those entries are set to enabled: false.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: dc2b3d4f-480b-4770-866f-75bdf8e1ba74

📥 Commits

Reviewing files that changed from the base of the PR and between f1fc457 and b5524c1.

📒 Files selected for processing (1)

• .coderabbit.yaml

[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 95-102: Update the .coderabbit.yaml Dockerfile checklist to
reflect the actual base image used: replace the specific instruction referencing
"python:3.13-alpine" (the string in the YAML under path: "**/Dockerfile") with
the correct base image used in the Dockerfile context
("python:3.13.3-slim-bookworm") or generalize to the 3.13 slim variant (e.g.,
"python:3.13.*-slim-bookworm") so the lint rule and the actual Dockerfile are
consistent.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 344dec17-a5b0-449f-bc46-d11f39ed5146

📥 Commits

Reviewing files that changed from the base of the PR and between b5524c1 and ee9babc.

📒 Files selected for processing (1)

• .coderabbit.yaml

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud