Code Review Practice

Written review guidelines, fast turnaround, small pull requests and comments that teach, plus the routines and skills that make reviews catch real problems for engineers and teams.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Code Review Practice, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Code Review Practice

Running code reviews that catch real problems, share knowledge and stay fast, with clear expectations for authors and reviewers alike.

  1. Written code review guidelines for the team
  2. Review turnaround baseline from the last 90 days
  3. Pull request template with context and test notes
  4. Code owners file and review routing
  5. Branch protection and required approval settings
  6. Severity labels for review comments
  7. Small pull request size agreement
  8. Author self-review before requesting review
  9. Personal reviewer checklist
  10. Daily review queue slot
  11. Weekly stale pull request sweep
  12. Reviewer load balancing rotation
  13. Monthly review health numbers
  14. Review comment themes log
  15. Monthly sample audit of merged pull requests
  16. Escaped defect trace back to review
  17. Quarterly review guideline refresh
  18. Writing review comments that are kind and specific
  19. Reading an unfamiliar diff efficiently
  20. Reviewing for correctness, edge cases and error paths
  21. Reviewing the tests in a pull request
  22. Spotting risky security patterns during review
  23. Reviewing database migrations safely
  24. Receiving review feedback well as an author
  25. Removing style nitpicks from human review
  26. One approval or two decision
  27. Stacked pull requests or a review tool change
  28. Live review sessions for large changes
  29. Disagreement escalation rule for reviews
  30. Splitting a large change into reviewable pieces
  31. Time to first review under one working day
  32. Screenshots and recordings for interface changes
  33. AI review assistant trial with guardrails
  34. Code review workshop for the team
  35. Reviewer calibration session
  36. Review plan for a major launch
  37. Annual code review experience survey
  38. Review of an inherited or handed-over codebase
  39. Earning review approval rights as a junior engineer
  40. Setting review norms as a new tech lead
  41. Code review across time zones
  42. Review practice for a solo or two-person team
  43. Introducing reviews to a team that never had them
  44. Reviewing contributions from outside the team
  45. Shadow reviewing to grow new reviewers
  46. Risk-based review tiers
  47. Review evidence for audited change control
  48. Reviewing AI-generated code
  49. Reviewing concurrency and performance-sensitive changes
  50. Honest review metrics dashboard

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Written code review guidelines for the team

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most review friction comes from unspoken expectations: one reviewer blocks on naming, another approves anything that compiles, and authors cannot tell which standard applies today.

First tasks

  • Collect any existing review rules from the wiki, chat pins and the contributing file
  • Ask the agent to draft a two-page guideline from those notes and your team's stack
  • Circulate the draft and ask every regular reviewer for three comments
  • Agree the final wording in the next team meeting and commit it

Review turnaround baseline from the last 90 days

Teams usually guess their review speed, and the guess is almost always kinder than the data. Pulling time to first review, time to approval and pull request size for the last 90 days from your hosting platform gives an honest starting point. Every later change to the review process can then be judged against numbers rather than feelings.

First tasks

  • Export the last 90 days of merged pull requests through the platform API or a reporting tool
  • Calculate median and 90th percentile time to first review in working hours
  • Summarise pull request size and the share above 400 changed lines
  • Record the baseline and the method so the next measurement is comparable

Pull request template with context and test notes

Reviewers waste the first ten minutes of many reviews working out why a change exists and how it was tested. A short pull request template asking for the problem, the approach, how to test it, the risk and any screenshots front-loads that context. Authors also catch their own gaps while filling it in, before anyone else has to point them out.

First tasks

  • List the questions reviewers ask most often in recent pull request threads
  • Write a template with why, what, testing, risk and screenshot sections
  • Commit the template in the location your hosting platform reads
  • Remove any section left blank in most of the first ten pull requests

Make it yours.

Install Code Review Practice, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.