code-review

Run automated linting, complexity, and code smell analysis on codebases.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/aaronbassett/claude-bell --skill code-review-aaronbassett
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/aaronbassett/claude-bell/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/aaronbassett/claude-bell --skill code-review-aaronbassett

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance for code review, combining automated analysis scripts and manual review checklists to improve code quality, performance, and architecture across languages.

Core Features & Use Cases

  • Automated Analysis Scripts: orchestrate linting, complexity analysis, and code smells detection across languages.
  • Manual Review Guidance: uses a structured checklist to ensure architecture, performance, and security considerations.
  • Unified Workflow: integrates automated results with human review for pre-commit or post-change reviews.

Quick Start

  • Run automated review: ./scripts/review_code.sh /path/to/code
  • Review output: cat .code-review-output/REVIEW.md
  • Check manual checklist: references/review-checklist.md
  • Address findings: Refactor as recommended

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code reviews for complexity and code smells?

Automate code reviews by running ./scripts/review_code.sh against your codebase to orchestrate linting, complexity analysis, and code smells detection. The script generates a markdown report containing automated findings and refactoring recommendations.

What is a code review checklist and when do I need it?

A code review checklist provides structured manual guidance to ensure architecture, performance, and security considerations are met. You need it before commits or PRs, after significant changes, or when analyzing unfamiliar legacy codebases.

Can I run static analysis and linting across multiple programming languages?

Yes, this static analysis and linting workflow applies across multiple programming languages. It orchestrates automated analysis scripts to check complexity and detect code smells regardless of the specific language used in your codebase.

What's the best way to review unfamiliar legacy codebases before a pull request?

The best way to review legacy codebases is combining automated analysis scripts with a manual review checklist. Run the automated script to detect code smells and complexity, then use the checklist to evaluate architecture and security.

How do I integrate automated code smells detection with human review?

Integrate automated code smells detection with human review through a unified workflow. Run the automated analysis script, review the generated markdown output, and then apply the manual review checklist to address architectural and performance considerations.

Does automated code review replace manual checklist evaluation for security and architecture?

No, automated code review does not replace manual checklist evaluation. The automated scripts handle linting, complexity, and code smells, while the manual checklist ensures thorough evaluation of architecture, performance, and security considerations.