quality-review

Review pull request diffs for code quality and test coverage.

2|Updated Mar 27, 2019
One-click install
npx skills add https://github.com/silcam/lessons-from-luke --skill quality-review-silcam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quality-review
Source: https://github.com/silcam/lessons-from-luke/tree/main/.claude/skills/quality-review
Command: npx skills add https://github.com/silcam/lessons-from-luke --skill quality-review-silcam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps reviewers catch code mistakes, weak tests, and hard-to-maintain changes before a pull request is merged.

Core Features & Use Cases

  • Code Quality Review: Finds correctness bugs, missing error handling, and maintainability problems.
  • Test Quality Review: Checks for weak coverage, brittle tests, and missing edge cases.
  • Manager-Friendly Output: Produces short, plain-English findings that are easy to scan and act on.
  • Use Case: Use it when a teammate opens a pull request and you need a fast review focused on quality, testing, and fix suggestions.

Quick Start

Ask the skill to review the latest pull request diff and return only the most important code quality findings.

Frequently Asked Questions about quality-review

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

FAQPage Schema
How do I review a pull request for code correctness and test quality?

You can review pull request diffs by analyzing them for correctness bugs and weak tests. This process filters known issues, verifies 100 percent test coverage, and outputs compressed plain-English findings to catch code mistakes before merging.

What is the best way to check for missing edge cases in test files?

Checking for missing edge cases requires a test quality review that evaluates pull request diffs for weak coverage and brittle tests. It verifies 100 percent coverage and outputs compressed plain-English findings to highlight missing edge cases.

Does code review for pull requests cover security and architecture concerns?

No, this code review specifically excludes security and architecture concerns. It focuses entirely on code quality, correctness, test quality, and common bug-fix scenarios while filtering known issues and verifying coverage.

Can I get plain-English output for code quality findings on GitHub pull requests?

Yes, you can get plain-English output for GitHub pull request code quality findings. The skill generates short, manager-friendly findings that are easy to scan and act on, focusing on quality, testing, and fix suggestions.

When do I need to filter known issues during a code review?

You need to filter known issues during a code review when analyzing pull request diffs to avoid repeating previously documented findings. This ensures the output contains only new, actionable severity-based results regarding code and test quality.