code-review

Name: code-review
Availability: InStock
Author: BoardPandas

Review codebases for correctness, naming, DRY, error handling, and type safety.

Updated Mar 7, 2026

Search Tags:#code quality #developer tools #quality assurance #static analysis #code review #bug detection

Ready to run

npx skills add https://github.com/BoardPandas/project-coder --skill code-review-boardpandas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/BoardPandas/project-coder/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/BoardPandas/project-coder --skill code-review-boardpandas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for thorough code quality checks, identifying potential bugs, style inconsistencies, and areas for improvement before they become major issues.

Core Features & Use Cases

Automated Code Scanning: Performs a detailed review across multiple categories like correctness, naming, and error handling.
Severity-Ranked Findings: Prioritizes issues into Critical, Warning, and Suggestion levels for efficient remediation.
Use Case: Before merging a new feature, run a code review to ensure it meets project standards and is free of common pitfalls, reducing the likelihood of post-deployment bugs.

Quick Start

Run a full code review of the entire project codebase.

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 comprehensive code review across my entire repository?▼

To perform a comprehensive code review, provide your repository paths and the tool will scan the codebase to identify issues in correctness, naming, DRY violations, error handling, type safety, test coverage, dead code, and consistency. It respects `.gitignore` rules during the scan.

What static analysis categories are checked during a code quality scan?▼

Static analysis categories checked during a code quality scan include correctness, naming conventions, DRY violations, error handling, type safety, test coverage, dead code, and consistency. Findings are prioritized into Critical, Warning, and Suggestion levels.

Can I limit the code review scope to specific directories instead of the full codebase?▼

Yes, you can limit the code review scope by providing specific paths. The analysis uses Glob, Grep, and Task tools to scan files, respecting `.gitignore` rules to ensure only the relevant directories within your codebase are analyzed.

How are detected bugs and code issues ranked for remediation?▼

Detected bugs and code issues are ranked by severity into Critical, Warning, and Suggestion levels. This severity-ranked prioritization helps developers efficiently remediate potential pitfalls and style inconsistencies before merging new features.

Does the code review tool respect my .gitignore rules?▼

Yes, the code review tool respects `.gitignore` rules when scanning your project paths. This ensures that static analysis and file scanning operations automatically exclude ignored files from the comprehensive code quality checks.