skills.rest
spencerpauly
spencerpaulyCOMMUNITY
Explore all skills by this author →
Website𝕏@spencerpaulyGitHub

reviewing-code

Review code changes and produce severity-ranked findings with file and line references.

672|104|Updated Apr 10, 2026
Search Tags:#testing#code review#performance#refactoring#maintainability#pull requests
One-click install
npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill reviewing-code-spencerpauly
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/reviewing-code
Command: npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill reviewing-code-spencerpauly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate code changes consistently so you can catch bugs, design problems, performance regressions, and missing tests before they merge.

Core Features & Use Cases

  • Reviews correctness by checking edge cases, error handling, async behavior, and loop logic.
  • Assesses maintainability, including naming, duplication, complexity, and function boundaries.
  • Flags performance and TypeScript issues, then organizes feedback by severity with clear fixes.
  • Use it on pull requests, refactors, bug fixes, and new features when you need actionable review comments.

Quick Start

Review the provided diff and return prioritized findings with file paths, line numbers, explanations, and suggested fixes.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema
How do I get structured code review feedback for a pull request?▼

Yes, you can review refactored code by analyzing the diff to assess maintainability issues like naming, duplication, complexity, and function boundaries. It provides severity-ranked findings with concise explanations and suggested fixes.

How do I check for performance regressions and edge cases in new features?▼

Checking for performance regressions and edge cases in new features involves evaluating the code changes for async behavior, loop logic, and error handling. It flags performance and TypeScript issues, organizing feedback by severity with clear fixes.

What is the best way to identify missing tests and error handling in bug fixes?▼

The best way to identify missing tests and error handling in bug fixes is to review the changes against criteria for correctness and testing. It produces prioritized findings with file and line references to highlight exactly where coverage is lacking.

Does this code review tool work without external dependencies or components?▼

Yes, this code review tool works without external dependencies or components. It operates directly on the provided diff to evaluate code changes consistently, catching bugs, design problems, and missing tests before they merge.

Can I use this to assess maintainability and naming conventions in my code?▼

Yes, you can use it to assess maintainability by checking naming conventions, code duplication, complexity, and function boundaries. It organizes this maintainability feedback by severity alongside correctness and performance issues.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

git-diff

Identify and review exact changes across git states with unified diff output.

Official
Advanced
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
alangebalangeb

code-review-workflow

Run pyscan, pyanalyze, ruff, and black to generate a unified markdown report.

Community
Intermediate
mqzkimmqzkim

test-generator

Generate Vitest unit and Playwright end-to-end tests from code diffs.

Community
Intermediate