playbooks

home / skills / sickn33 / antigravity-awesome-skills / code-review-excellence

code-review-excellence skill

/skills/code-review-excellence

This skill helps you elevate code reviews into knowledge sharing by delivering actionable feedback focused on correctness, security, and maintainability.

This is most likely a fork of the code-review-excellence skill from xfstudio
npx playbooks add skill sickn33/antigravity-awesome-skills --skill code-review-excellence

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.4 KB
---
name: code-review-excellence
description: Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.
---

# Code Review Excellence

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.

## Use this skill when

- Reviewing pull requests and code changes
- Establishing code review standards
- Mentoring developers through review feedback
- Auditing for correctness, security, or performance

## Do not use this skill when

- There are no code changes to review
- The task is a design-only discussion without code
- You need to implement fixes instead of reviewing

## Instructions

- Read context, requirements, and test signals first.
- Review for correctness, security, performance, and maintainability.
- Provide actionable feedback with severity and rationale.
- Ask clarifying questions when intent is unclear.
- If detailed checklists are required, open `resources/implementation-playbook.md`.

## Output Format

- High-level summary of findings
- Issues grouped by severity (blocking, important, minor)
- Suggestions and questions
- Test and coverage notes

## Resources

- `resources/implementation-playbook.md` for detailed review patterns and templates.

Overview

This skill teaches practical, high-impact code review practices to produce constructive feedback, catch defects early, and foster team learning while preserving morale. It focuses on systematic checks for correctness, security, performance, and maintainability and provides a clear output template for reviewers.

How this skill works

Read the pull request context, requirements, and test signals first, then scan for correctness, security risks, performance regressions, and maintainability concerns. Produce a concise summary, group findings by severity (blocking, important, minor), and include actionable suggestions, rationale, and targeted questions. Add test and coverage notes and recommend follow-up steps or checklist items when needed.

When to use it

  • Reviewing pull requests or code changes
  • Defining or enforcing code review standards
  • Mentoring developers through PR feedback
  • Auditing code for correctness, security, or performance
  • Preparing release branches or high-risk deployments

Best practices

  • Start with the PR description, tests, and acceptance criteria before reading diffs
  • Prioritize blocking issues (correctness, security) and label others clearly
  • Give actionable suggestions with minimal required changes and clear rationale
  • Balance critique with recognition of good patterns and successful solutions
  • Ask clarifying questions rather than assuming intent when behavior is unclear
  • Reference tests, benchmarks, or small reproductions to demonstrate issues

Example use cases

  • A reviewer catching an SQL injection vector and suggesting parameterized queries and tests
  • Establishing a team checklist for performance regressions and CI benchmarks
  • Mentoring a junior engineer by annotating a PR with incremental improvement steps
  • Auditing a feature branch for missing edge-case tests and proposing concrete test cases
  • Triage of a large refactor: summarizing risk areas and required follow-up tasks

FAQ

What should a high-level summary include?

State the PR purpose, overall correctness judgment, main risks, and whether it’s merge-ready with minor fixes or requires blocking fixes.

How do I indicate severity effectively?

Use three tiers: blocking (must-fix before merge), important (should fix), and minor (optional or stylistic). Provide impact rationale and suggested remediation for each item.