code-review

Review code changes for bugs, style issues, and best practices.

3|Updated Dec 27, 2025

Search Tags:#quality assurance #code review #pull request #coding standards #bug detection

Ready to run

npx skills add https://github.com/JIsaiah/Nostargia --skill code-review-jisaiah

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/JIsaiah/Nostargia/tree/main/.agent/skills/code-review
Command: npx skills add https://github.com/JIsaiah/Nostargia --skill code-review-jisaiah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure code quality by identifying potential bugs, style inconsistencies, and areas for improvement before code is merged.

Core Features & Use Cases

Bug Detection: Identifies common programming errors and logical flaws.
Style Enforcement: Checks adherence to project-specific coding conventions.
Best Practice Adherence: Recommends improvements based on established software development principles.
Use Case: When a pull request is submitted, use this skill to perform a thorough review, providing actionable feedback to the author.

Quick Start

Review the code changes in the current pull request for correctness and style.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I perform a code review on a pull request?▼

Code review evaluates pull request changes using a predefined checklist to identify bugs, style issues, and best practice violations. It inspects code correctness, edge cases, style, and performance to provide actionable feedback before merging.

What is static code analysis for bug detection?▼

Static code analysis for bug detection examines code changes to find logical flaws and style inconsistencies before merging. It applies a systematic approach to inspect correctness, edge cases, and performance, recommending improvements based on best practices.

How do I check code changes for coding standards and style issues?▼

Checking code changes for coding standards involves reviewing pull requests against project-specific conventions using a predefined checklist. This systematic inspection enforces style adherence and identifies potential bugs before merging.

Does this code review process support quality assurance for any programming language?▼

This code review process supports quality assurance by applying a systematic inspection covering correctness, edge cases, style, and performance. It evaluates code changes for bugs and best practice adherence across general software engineering contexts.

What's the best way to catch bugs and edge cases before merging code?▼

The best way to catch bugs and edge cases before merging is to perform a thorough pull request review using a predefined checklist. This systematic code inspection identifies common programming errors, logical flaws, and style inconsistencies to ensure quality.

Why does my code review need a predefined checklist?▼

A code review needs a predefined checklist to ensure a systematic approach to inspecting correctness, edge cases, style, and performance. It guarantees consistent bug detection, style enforcement, and adherence to established best practices.