Repository navigation
rfc: dedicated review time and stacked PRs - #18
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
bajtos
approved these changes
Aug 3, 2026
|
|
||
| ## Proposal 1: dedicated review time | ||
|
|
||
| Each of us holds one hour a day on the calendar for review, checks the review queue before starting new build work, and gives a first response to any review request within one business day. Google's measured cost is about 3 hours a week, so an hour a day is deliberately above steady state: we have a review backlog to drain and agents multiplying our output. Revisit the number in a month. |
Member
There was a problem hiding this comment.
I agree with everything proposed here.
I suggest these additions to consider:
- Configure CODEOWNERS in each repository, so that every new PR automatically requests review from at least one person.
- Monitor "time to first response to a review request" on a per-user and team-wide basis. Every week, an automation should post a message to our eng Slack channel with a list of p50 & p90 for each team member.
- Implement basic alerting. For example: at noon in my local time, if there are any outstanding review requests from yesterday or before, send me a Slack DM with the list of review requests needing my attention.
Member
There was a problem hiding this comment.
I agree with Miro, simple slack reminder would be great.
Comment on lines
+34
to
+36
| A PR should be reviewable in under an hour, which the evidence puts at roughly 400 changed lines, though the content is just as important -- critical auth logic takes longer than code-gen'd serialization for example. Therefore, bigger work must ship as a stack of dependent PRs, each one a reviewable step. | ||
|
|
||
| The norm binds our agents too. Each active repo's AGENTS.md gets an instruction that work expected to exceed the guide ships as a stack, and Claude Code gets the stack tooling below. |
Member
There was a problem hiding this comment.
Is it worth adding some automation here as well? E.g. a GHA workflow that posts a warning comment to the PR discussion if the diff is larger than 400 lines.
pyropy
approved these changes
Aug 3, 2026
pyropy
left a comment
pyropy
left a comment
Member
There was a problem hiding this comment.
Great initiative, I agree with everything in this RFC.
alanshaw
approved these changes
Aug 3, 2026
|
|
||
| ## Decisions needed | ||
|
|
||
| - **The hour.** I propose one hour a day. Google's measured average is about three hours a week, so this is deliberately generous while the backlog drains. |
Member
There was a problem hiding this comment.
Agree as a baseline, I spend significantly more than this daily already though.
Contributor
Author
There was a problem hiding this comment.
but you are one of the good ones
| ## Decisions needed | ||
|
|
||
| - **The hour.** I propose one hour a day. Google's measured average is about three hours a week, so this is deliberately generous while the backlog drains. | ||
| - **Pilot now vs. wait.** The GitHub preview is days old and will have sharp edges; spr covers the gaps. I propose pilot now. |
|
|
||
| - **The hour.** I propose one hour a day. Google's measured average is about three hours a week, so this is deliberately generous while the backlog drains. | ||
| - **Pilot now vs. wait.** The GitHub preview is days old and will have sharp edges; spr covers the gaps. I propose pilot now. | ||
| - **Size guardrails.** Social norm only, or a soft CI warning above ~400 changed lines? I lean social to start. |
parkan
self-requested a review
August 4, 2026 14:11
parkan
approved these changes
Aug 4, 2026
Co-authored-by: Miroslav Bajtoš <oss@bajtos.net>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📖 Preview
Summary
Two commitments to fix our review bottleneck: an hour a day of calendar-held review time with a one-business-day first response, and stacked PRs for anything bigger than an hour's review — recommending GitHub's native stacked pull requests (with our Claude Code workflows taught to produce stacks), spr as fallback, Graphite in reserve.