skills.rest
esafirm
esafirmCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review-and-quality

Review code changes for defects, quality, and merge readiness.

4|Updated Aug 18, 2016
Search Tags:#architecture#quality assurance#code review#performance#pull requests#security review
One-click install
npx skills add https://github.com/esafirm/dotfiles --skill code-review-and-quality-esafirm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/esafirm/dotfiles/tree/main/.claude/skills/code-review-and-quality
Command: npx skills add https://github.com/esafirm/dotfiles --skill code-review-and-quality-esafirm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate code changes before merge so defects, weak design choices, security issues, and performance regressions are caught early instead of reaching the main branch.

Core Features & Use Cases

  • Multi-axis review: Checks correctness, readability, architecture, security, and performance in one pass.
  • Merge readiness decisions: Produces clear approve or request-changes guidance with severity-labeled findings.
  • Use Case: A teammate submits a bug fix and you want a fast but thorough review that verifies the patch, the regression test, and any hidden risks before approval.

Quick Start

Review the proposed code change against the five review axes and return prioritized findings with a final merge recommendation.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
How do I review code changes for defects and merge readiness?▼

To review code changes for merge readiness, evaluate the proposed diff against five axes: correctness, readability, architecture, security, and performance. Return prioritized findings with explicit severity labels and a final approve or request-changes recommendation.

How do I check a pull request for security issues and performance regressions?▼

Checking a pull request for security issues and performance regressions requires a multi-axis review. Evaluate the code changes for vulnerabilities and speed degradations, assign severity labels to findings, and verify regression tests before approving the merge.

Can I use this to review agent-generated edits and refactors?▼

Yes, you can review agent-generated edits and refactors. The review applies to bug fixes and automated code changes across both frontend and backend repositories, ensuring any machine-generated logic meets architecture and quality standards before merging.

What is the best way to evaluate architecture quality in a bug fix?▼

The best way to evaluate architecture quality in a bug fix is to review the patch against established design patterns alongside correctness and security. Require explicit severity labels for any architectural flaws found before granting merge approval.

Why do I need explicit severity labels in a code review?▼

Explicit severity labels are needed in a code review to prioritize findings and produce clear merge readiness decisions. They help distinguish minor readability issues from critical security vulnerabilities, ensuring high-risk defects are resolved before the main branch merge.

Related Skills

Explore More Software Engineering Skills→
askaretaskaret

pr-review

Review pull requests for correctness, security, performance, and maintainability.

Community
Intermediate
pmatospmatos
2

auto-merge-dependabot

Classify and merge Dependabot PRs based on risk criteria.

Community
Intermediate
nikblanchetnikblanchet

exhaustive-testing

Plan and implement unit, integration, regression, end-to-end, and manual test coverage.

Community
Basic
NorkzYTNorkzYT
2

sast-configuration

Configure and tune SAST tools for automated vulnerability detection in CI/CD pipelines.

Community
Advanced