Code Reviewer Best Practices

Sub-skill of code-reviewer: Best Practices.

vamseeachanta 323ba43 602 B Updated

File contents

Best Practices

Best Practices

Do

  1. Review in small batches (200-400 lines ideal)
  2. Focus on logic, not style (use linters)
  3. Ask questions rather than demand changes
  4. Acknowledge good code
  5. Provide specific, actionable feedback
  6. Test the changes locally when possible

Don't

  1. Nitpick style issues
  2. Rewrite author's code in comments
  3. Leave vague feedback ("this is wrong")
  4. Review when fatigued
  5. Approve without understanding
  6. Block for preferences, not issues

vamseeachanta/workspace-hub/tree/main/.agents/skills/_archive/development/code-reviewer/best-practices commit 323ba43973

Frequently asked questions

npx skillmds@latest add vamseeachanta/code-reviewer-best-practices