chore: expand CodeRabbit config with per-package review guidance

[SaharPak]

Summary

• Add per-package path_instructions so CodeRabbit reviews packages/core, packages/cli, and packages/web (and markdown docs) with the right context.
• Enable the ESLint and markdownlint tools so reviews lean on the linting the repo already uses.
• Ignore build/dependency output (dist, .turbo, node_modules, snapshots) on top of the existing lockfile filter.
• Disable the review poem and turn on knowledge base learnings.

This builds on the existing minimal .coderabbit.yaml on main.

Notes

CodeRabbit reads its config from the PR base branch, so these settings take effect for new PRs once this is merged into main.

Summary by CodeRabbit

• Chores
  • Updated code review configuration to adjust review behavior, expand path filtering exclusions, and add scoped review guidance for specific packages and file types.

[coderabbitai]

📝 Walkthrough

Walkthrough

The .coderabbit.yaml configuration file is updated to adjust CodeRabbit's review behavior. The schema reference URL is modernized, top-level settings disable poem summaries and early access features, path filters exclude build output and generated files, and new path-scoped instructions provide targeted review guidance for core packages and documentation.

Changes

Configuration Updates

Layer / File(s)	Summary
Review settings and path-scoped instructions .coderabbit.yaml	Schema reference updated to coderabbit.ai/integrations URL; early_access set to false and reviews.poem disabled; path_filters extended with exclusions for dist, .turbo, node_modules, and *.snap files; new path_instructions section added with scoped review guidance for packages/core, packages/cli, packages/web, and Markdown files.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: expanding the CodeRabbit config with per-package review guidance, which is the primary focus of the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/coderabbit-config

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.coderabbit.yaml (1)

16-21: 💤 Low value

Consider excluding additional common artifacts.

The current exclusions cover the main build artifacts. You might also consider excluding:

• **/.next/** (if using Next.js)
• **/coverage/** (test coverage reports)
• **/.cache/** (various tool caches)

Only add these if they're relevant to your project structure.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.coderabbit.yaml around lines 16 - 21, Update the path_filters list to add
additional common artifact excludes if relevant: add entries like
"!**/.next/**", "!**/coverage/**", and "!**/.cache/**" alongside the existing
filters (e.g., the current path_filters containing "!**/pnpm-lock.yaml",
"!**/dist/**", "!**/.turbo/**", "!**/node_modules/**", "!**/*.snap") so these
folders are ignored by the CI/toolchain when applicable to the project.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.coderabbit.yaml:
- Around line 41-45: The repo enables eslint and markdownlint in
.coderabbit.yaml but lacks repository-level configurations; add or confirm
ESLint config (e.g., create an .eslintrc.* or eslint.config.* file or add an
"eslintConfig" section to package.json) and add a markdownlint config (e.g.,
.markdownlintrc, .markdownlint.json or markdownlint settings in package.json) so
the tools referenced under tools: eslint and markdownlint can run; ensure the
config files are committed to the repo root and include any required plugins or
rules referenced by your codebase.

---

Nitpick comments:
In @.coderabbit.yaml:
- Around line 16-21: Update the path_filters list to add additional common
artifact excludes if relevant: add entries like "!**/.next/**",
"!**/coverage/**", and "!**/.cache/**" alongside the existing filters (e.g., the
current path_filters containing "!**/pnpm-lock.yaml", "!**/dist/**",
"!**/.turbo/**", "!**/node_modules/**", "!**/*.snap") so these folders are
ignored by the CI/toolchain when applicable to the project.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 05e584d5-2589-450a-8268-2908e6b1da8e

📥 Commits

Reviewing files that changed from the base of the PR and between facea8e and b99db73.

📒 Files selected for processing (1)

• .coderabbit.yaml

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify that ESLint and markdownlint configuration files exist

echo "=== ESLint config ==="
fd -t f -d 2 '\.eslintrc\.(js|cjs|json|yaml|yml)$|eslint\.config\.(js|mjs|cjs)$' . || echo "No .eslintrc.* or eslint.config.* found"
rg -l '"eslintConfig"' package.json || echo "No eslintConfig in package.json"

echo "=== markdownlint config ==="
fd -t f -d 2 '\.markdownlint\.(json|yaml|yml|cjs|mjs)$|\.markdownlintrc$' . || echo "No .markdownlint config found"

Repository: TechImmigrants/cv-builder

Length of output: 151

---

Ensure ESLint/markdownlint configs exist in the repo when enabling them in .coderabbit.yaml.

.coderabbit.yaml enables eslint and markdownlint, but package.json contains no eslintConfig. Add or confirm the repo-level ESLint config (.eslintrc.* or eslint.config.*) and markdownlint config (.markdownlintrc* / markdownlint settings) so CodeRabbit can run both tools correctly.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.coderabbit.yaml around lines 41 - 45, The repo enables eslint and
markdownlint in .coderabbit.yaml but lacks repository-level configurations; add
or confirm ESLint config (e.g., create an .eslintrc.* or eslint.config.* file or
add an "eslintConfig" section to package.json) and add a markdownlint config
(e.g., .markdownlintrc, .markdownlint.json or markdownlint settings in
package.json) so the tools referenced under tools: eslint and markdownlint can
run; ensure the config files are committed to the repo root and include any
required plugins or rules referenced by your codebase.

[amirbahador-hub]

No a lot of them are the prompts templates not the Docs

[amirbahador-hub]

This doesn't match with our cli, because our cli is not traditional cli it's prompt as code, it uses users code agents to do this

[amirbahador-hub]

Core is orchestrator, the logic is everywhere in intelligence, ingestions, server, frontend, prompts and so on

[SaharPak]

Thanks for expanding the CodeRabbit config! Per-package review guidance is now in the MVP integration branch. This makes automated PR review much more useful going forward. Appreciate the polish!