review-code

Review code across files and apply approved changes directly to source files.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Suniljit/personal-toolkit --skill review-code-suniljit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/review-code
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill review-code-suniljit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs thorough, opinionated code reviews that identify bugs, inefficiencies, and SRP violations, and then applies changes directly to the files after user confirmation.

Core Features & Use Cases

  • Comprehensive code reviews that surface bugs, anti-patterns, and opportunities for reuse while preserving original behavior.
  • Enforces Single Responsibility Principle by suggesting clean separations and guiding non-destructive refactors.
  • Safe in-place edits after user approval, with clear reporting of findings to the user.

Quick Start

Review your codebase and apply approved changes directly to your repository.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I perform a code review with in-place fixes?

Code review with in-place fixes identifies bugs and SRP violations, then applies changes directly to source files after explicit user confirmation. It preserves original behavior while minimizing introduced changes across single or multi-file projects.

What is Single Responsibility Principle enforcement in refactoring?

Single Responsibility Principle enforcement in refactoring suggests clean separations and guides non-destructive refactors to ensure each module handles one responsibility. This surfaces anti-patterns and code reuse opportunities while preserving original behavior.

Can I use static analysis for multi-file projects across different languages?

Static analysis for multi-file projects supports various programming languages from single-file scripts to full repositories. It performs comprehensive reviews to surface inefficiencies and bugs without requiring specific dependencies.

Does code review require confirmation before applying changes to source files?

Code review requires explicit user confirmation before applying changes to source files. It reports findings clearly and only writes approved modifications directly to the repository, ensuring safe non-destructive refactors.

What's the best way to find code reuse opportunities during a refactor?

Finding code reuse opportunities during a refactor involves comprehensive static analysis that surfaces anti-patterns and duplicated logic. The review enforces SRP by suggesting clean separations and guiding non-destructive refactors while preserving behavior.

Why does my code review not working properly for multi-file projects?

Code review for multi-file projects requires explicit confirmation before applying changes and preserves original behavior while minimizing introduced modifications. If changes are not applied, ensure user approval was granted and source files are accessible.