skills.rest
jampissarandev
jampissarandevCOMMUNITY
Explore all skills by this author →
GitHub

code-review-and-quality

Reviews code changes across correctness, readability, architecture, security, and performance before merge.

Updated Jun 23, 2026
Search Tags:#code review#pull request#refactoring#software quality#security review#quality gates#merge checklist
One-click install
npx skills add https://github.com/jampissarandev/Expense-Tracker --skill code-review-and-quality-jampissarandev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/jampissarandev/Expense-Tracker/tree/main/.github/skills/code-review-and-quality
Command: npx skills add https://github.com/jampissarandev/Expense-Tracker --skill code-review-and-quality-jampissarandev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code merged without structured review accumulates defects, security vulnerabilities, and architectural debt. This Skill enforces a consistent multi-axis review process so every change is evaluated against the same quality gates before entering the main branch. ## Core Features & Use Cases - Five-Axis Review: Evaluates every change for correctness, readability, architecture, security, and performance with concrete checklists per axis. - Severity-Labeled Feedback: Categorizes findings as Critical, Required, Nit, Optional, or FYI so authors know exactly what must be addressed before merge. - Change Sizing & Splitting Guidance: Defines target change sizes (~100 lines) and provides stacking, horizontal, and vertical splitting strategies for oversized changes. - Use Case: Before merging a pull request that adds a new API endpoint, run the review checklist to verify tests cover edge cases, inputs are validated, no N+1 queries exist, and the change description stands alone in version control history. ## Quick Start Review this pull request across correctness, readability, architecture, security, and performance, and label each finding by severity.

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 a pull request before merging?▼

Review a pull request by first understanding its intent, then checking tests, then walking the implementation across five axes: correctness, readability, architecture, security, and performance. Label every finding by severity so the author knows what must be fixed before merge.

What should a code review checklist include?▼

A code review checklist should cover correctness against the spec, edge case and error handling, test adequacy, naming and readability, architectural fit, input validation and secret handling, and performance issues like N+1 queries or missing pagination.

How large should a pull request be for effective review?▼

A pull request should target around 100 changed lines, with 300 acceptable for a single logical change. Changes near 1000 lines should be split using stacking, file-group, horizontal, or vertical splitting strategies.

When should a code review reject a change?▼

Reject a change when it has Critical issues like security vulnerabilities, data loss, or broken functionality, or unresolved Required findings. Approve when the change improves overall code health even if it is not perfect.

Does AI-generated code need code review?▼

AI-generated code needs more scrutiny, not less, because it is confident and plausible even when wrong. Review it across all five axes, verify tests actually test behavior, and never rubber-stamp with an unexamined approval.

Related Skills

Explore More Software Engineering Skills→
yjzhang2003yjzhang2003
26

web-monitor-safety-check

Validate git diffs against security and operational constraints.

Community
Intermediate
daniyarseifolladaniyarseifolla

adapter-gitlab

Automate GitLab CI/CD merge requests, pipeline monitoring, and deploy triggers.

Community
Advanced
Devsoul2026Devsoul2026
150

requesting-code-review

Automate pre-commit verification with static analysis, tests, and lint checks.

Community
Advanced
monoesmonoes
15

pair-programming

Coordinate role-based pair programming sessions with continuous code review and testing.

Official
Advanced