code-review-excellence

Identify bugs, security risks, test gaps, and maintainability issues in pull requests.

Updated May 16, 2026
One-click install
npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill code-review-excellence-p-o-ke-nae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory/tree/main/.github/skills/code-review-excellence
Command: npx skills add https://github.com/p-o-ke-nae/pokemondamagecalculatorforstory --skill code-review-excellence-p-o-ke-nae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn code reviews into a reliable way to catch bugs, improve design, strengthen tests, and share knowledge without hurting team morale.

Core Features & Use Cases

  • Constructive Review Feedback: Frame comments as specific, actionable suggestions that focus on the code rather than the person.
  • Systematic Review Workflow: Evaluate PR context, architecture, file organization, logic correctness, security, performance, and maintainability in a consistent sequence.
  • Review Quality Standards: Distinguish blocking issues from minor nits, use checklists to stay thorough, and keep reviews efficient and fair.
  • Use Case: A reviewer can assess a pull request for edge cases, missing tests, injection risks, and design tradeoffs, then leave prioritized comments that help the author improve the change confidently.

Quick Start

Review the pull request with the code-review-excellence skill and provide prioritized feedback on correctness, security, testing, and maintainability.

Frequently Asked Questions about code-review-excellence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request for security risks and test gaps?

To review a pull request for security risks and test gaps, evaluate PR context, architecture, logic correctness, and maintainability in a consistent sequence using checklist-driven analysis to identify injection risks and missing tests.

What is the best way to give constructive code review feedback without hurting team morale?

Constructive code review feedback frames comments as specific, actionable suggestions that focus on the code rather than the person, using severity-based prioritization to distinguish blocking issues from minor nits while supporting team learning.

How do I structure a systematic code review workflow for architecture checks?

A systematic code review workflow evaluates PR context, architecture, file organization, logic correctness, security, performance, and maintainability in a consistent sequence to catch bugs and improve design across software projects.

Can I use checklist-driven analysis to prioritize bugs in pull requests?

Checklist-driven analysis prioritizes bugs in pull requests by applying severity-based prioritization to distinguish blocking issues from minor nits, ensuring reviews remain thorough, efficient, and fair for the author.

When should I use severity-based prioritization in code reviews?

Severity-based prioritization in code reviews should be used to distinguish blocking issues from minor nits, helping reviewers leave prioritized comments that allow authors to improve changes confidently and efficiently.

Does constructive feedback in code review help with developer mentoring?

Constructive feedback in code review supports developer mentoring by providing collaborative guidance that focuses on specific, actionable suggestions, enabling team learning while assessing edge cases and design tradeoffs.