Skip to content

docs(rules): judge work by value delivered, not effort spent#127

Merged
zolotokrylin merged 2 commits into
mainfrom
docs/rules-value-over-effort
Jul 15, 2026
Merged

docs(rules): judge work by value delivered, not effort spent#127
zolotokrylin merged 2 commits into
mainfrom
docs/rules-value-over-effort

Conversation

@zolotokrylin

Copy link
Copy Markdown
Member

Problem

Work is justified by hours spent rather than value delivered, so mechanical tasks a tool does in minutes still bill full cost. Reviewers had no rule to cite when rejecting high-effort, low-value work.

Solution

Adds DEV-440 in the Review category: work is judged by value against cost, not effort, and mechanical work is directed to AI. Indexed in the rules README.

@holdex

holdex Bot commented Jul 15, 2026

Copy link
Copy Markdown

Time Submission Status

Member # Time Running Total Status Last Update
zolotokrylin 11min ✅ Submitted Jul 15, 2026, 7:56 AM

Submit or update total time with:

@holdex pr submit-time 2h

Add time on top of previous submission with:

@holdex pr add-time 1h30m

See available commands to help comply with our Guidelines.

@zolotokrylin zolotokrylin self-assigned this Jul 15, 2026
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@zolotokrylin, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ab5f38ba-3177-4ab4-8513-7b506fc3113d

📥 Commits

Reviewing files that changed from the base of the PR and between d86fd22 and 6173738.

📒 Files selected for processing (2)
  • docs/rules/DEV-440.md
  • docs/rules/README.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/rules-value-over-effort

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

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

@zolotokrylin
zolotokrylin marked this pull request as ready for review July 15, 2026 07:55
@zolotokrylin

Copy link
Copy Markdown
Member Author

@holdex pr add-time 11m

@zolotokrylin
zolotokrylin merged commit 6556af8 into main Jul 15, 2026
4 checks passed
@zolotokrylin
zolotokrylin deleted the docs/rules-value-over-effort branch July 15, 2026 07:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Problem: reviewers can't reject high-effort low-value work

1 participant