reviewing-code

Name: reviewing-code
Availability: InStock
Author: pavkabrika

Identify and report code issues with file paths, line numbers, and suggested fixes.

1|Updated Jun 23, 2022

Search Tags:#performance #debugging #maintainability #best-practices #quality-assurance #code-review

Ready to run

npx skills add https://github.com/PavkaBrika/debtbookapp --skill reviewing-code-pavkabrika

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/PavkaBrika/debtbookapp/tree/main/.cursor/skills/reviewing-code
Command: npx skills add https://github.com/PavkaBrika/debtbookapp --skill reviewing-code-pavkabrika

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers systematically review code to identify correctness issues, maintainability concerns, performance problems, and deviations from best practices, reducing time to safe, high-quality releases.

Core Features & Use Cases

Thorough correctness checks: edge cases, error handling, and data boundaries.
Maintainability improvements: naming clarity, modularization, and duplication reduction.
Performance and reliability assessment: potential bottlenecks, unnecessary re-renders, and resilience considerations.
Use case example: when reviewing a PR, analyze changes and produce a prioritized, actionable list of fixes.

Quick Start

Analyze the provided code changes and return a structured, actionable review.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema

How do I review code changes for correctness and maintainability?▼

To review code changes for correctness and maintainability, analyze the diffs to identify edge cases, error handling issues, and naming clarity. Produce a prioritized, actionable list of fixes with file paths and line numbers to ensure high-quality releases.

What is included in a thorough code review?▼

A thorough code review includes correctness checks for data boundaries, maintainability improvements like modularization, performance bottleneck identification, and adherence to best practices. It returns clear feedback with suggested fixes.

How do I check my code diff for performance bottlenecks and best practices?▼

Checking a code diff for performance bottlenecks and best practices involves assessing potential unnecessary re-renders, resilience considerations, and deviations from project standards. Apply this to changes across languages and project structures.

Can I use an automated code review for large features across different languages?▼

Yes, you can use automated code review for large features across different languages. It analyzes changes from small diffs to large features, identifying duplication, modularization opportunities, and edge cases regardless of project structure.

What is the best way to get actionable feedback on a pull request?▼

The best way to get actionable feedback on a pull request is to analyze the provided code changes and return a structured review. This produces a prioritized list highlighting correctness, maintainability, and performance issues.