Add estimate_code_review_effort to yaml-template.md

[tomaszhanc]

• This adds missing estimate_code_review_effort to the YAML template reference.
• Schema exposes this attribute

Summary by CodeRabbit

• Documentation
  • Updated the configuration template documentation to include a new option, estimate_code_review_effort, under the reviews section. This option is enabled by default.

[coderabbitai]

📝 Walkthrough

Walkthrough

The .coderabbit.yaml configuration template documentation was updated to introduce a new boolean option, estimate_code_review_effort, within the reviews section. This option is set to true by default. No other configuration changes were made.

Changes

Cohort / File(s)	Change Summary
YAML Template Documentation docs/reference/yaml-template.md	Added estimate_code_review_effort: true to the reviews section of the configuration template.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A toggle appears in the YAML night,
For review effort, set to true by default—just right!
A single line joins the doc parade,
Making CodeRabbit's wisdom a bit more displayed.
One small change, but oh what delight!
The config grows smarter before our sight.
🐇✨

Pre-Merge Checks (2 passed, 1 warning)

❌ Failed Checks (1 warning)

Check Name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The description is too brief and lacks context, details about the new option’s behavior, default value, usage examples, and rationale.	Expand the description to explain the purpose of estimate_code_review_effort, its default behavior, usage examples, and motivation for the change, and add a pull request template to the repository to ensure consistent, detailed PR descriptions.

✅ Passed Checks (2 passed)

Check Name	Status	Explanation
Title Check	✅ Passed	The title clearly indicates adding the estimate_code_review_effort field to the yaml-template.md documentation and accurately reflects the change.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
• 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 src/utils.ts and explain its main purpose.
  • @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 comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• 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

Documentation and Community

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

[coderabbitai]

Actionable comments posted: 0

🔭 Outside diff range comments (1)

docs/reference/yaml-template.md (1)

7-8: Tighten wording to remove the double “as”

Current sentence is grammatically awkward (“as-is as a”). Let’s smooth it out:

-If used as-is as a `.coderabbit.yaml` file, then this template sets the default, recommended values for [all CodeRabbit repository options](/reference/configuration).
+If you use this template as-is for your `.coderabbit.yaml` file, it sets the default, recommended values for [all CodeRabbit repository options](/reference/configuration).

Documentation quality is a blocker, so please amend.

🧹 Nitpick comments (1)

docs/reference/yaml-template.md (1)

34-35: Schema & docs need to be kept in sync with the new flag

Great to see estimate_code_review_effort added.
Please double-check two follow-ups before merging:

1. schema.v2.json must expose this new property, otherwise users will see validation errors in their editors.
2. The reference documentation page that enumerates every reviews key should include a short description of what this flag does and its default value.

Without those updates, the template and docs will drift out of sync.
[tagging]

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ee5a787 and 24bbd14.

📒 Files selected for processing (1)

• docs/reference/yaml-template.md (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: jmacdotorg
PR: coderabbitai/coderabbit-docs#0
File: :0-0
Timestamp: 2025-07-30T16:14:47.514Z
Learning: In the coderabbitai/coderabbit-docs repository, spelling and grammar errors in documentation should be treated as bugs that require correction prior to merge, not as minor typos or nitpick suggestions. Documentation has higher quality standards than typical code reviews.

🔍 MCP Research (1 server)

PostHog:

• Documented example YAML structure for estimating code review effort includes factors such as lines of code, complexity rating, familiarity with codebase, number of dependencies, documentation availability, and time estimate in hours. (Source: PostHog docs search result on "estimate_code_review_effort yaml-template")

[jmacdotorg]

LGTM, thank you!