code-review-excellence

Review Python and TypeScript pull requests for bugs, security risks, and maintainability.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Jhabbig/Habbig --skill code-review-excellence-jhabbig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/Jhabbig/Habbig/tree/main/.claude/plugins/wshobson/developer-essentials/skills/code-review-excellence
Command: npx skills add https://github.com/Jhabbig/Habbig --skill code-review-excellence-jhabbig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers give useful, consistent feedback on pull requests without missing bugs, security issues, or maintainability problems, while keeping collaboration constructive.

Core Features & Use Cases

  • Systematic review workflow: Checks context, architecture, file organization, tests, and line-level logic in a repeatable sequence.
  • High-signal feedback: Uses severity labels and collaborative wording to separate blocking issues from suggestions and nits.
  • Use cases: Reviewing feature branches, mentoring junior developers, setting team review standards, and evaluating security or architecture changes.

Quick Start

Use this skill to review the pull request, summarize the strongest risks and strengths, and return prioritized feedback with a clear approve, comment, or request changes verdict.

Frequently Asked Questions about code-review-excellence

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

FAQPage Schema
How do I do a systematic pull request review without missing bugs or security risks?

A systematic pull request review requires a checklist-driven analysis covering context, architecture, tests, and line-level correctness to catch bugs and security risks. Using severity labels helps separate blocking issues from suggestions and nits.

How do I write constructive code review feedback for junior developers?

Constructive code review feedback for junior developers uses collaborative wording and severity labels to separate blocking issues from minor suggestions. Applying a structured review checklist ensures mentoring focuses on maintainability and logic without overwhelming the author.

What is the best way to establish team review standards for Python and TypeScript projects?

Establishing team review standards for Python and TypeScript projects involves applying a repeatable sequence of architecture checks, test coverage evaluation, and line-level correctness validation. Using severity labeling ensures consistent, structured feedback across the entire engineering workflow.

Can I use a code review checklist to evaluate architecture and security changes?

Yes, a code review checklist can evaluate architecture and security changes by running through structured phases that cover context, design, and tests. This checklist-driven analysis identifies maintainability issues and security risks early in the review workflow.

Why does my PR review feedback lack high signal and prioritization?

PR review feedback lacks high signal when it does not use severity labels to distinguish blocking issues from suggestions. Implementing a structured review workflow with prioritized feedback and clear verdicts ensures high-signal, actionable outcomes.