bms:code-review

Identify correctness, edge-case, and maintainability issues in code.

68|14|Updated Dec 21, 2017

Search Tags:#consistency #maintainability #analysis #quality #edge-cases #code-review #tests

Ready to run

npx skills add https://github.com/benmatselby/dotfiles --skill bms-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bms:code-review
Source: https://github.com/benmatselby/dotfiles/tree/main/agents/skills/code-review
Command: npx skills add https://github.com/benmatselby/dotfiles --skill bms-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Harsh, constructive code reviews that identify issues, risks, and improvement opportunities to elevate code quality and maintainability.

Core Features & Use Cases

Thorough correctness & edge-case analysis: detects logic errors, boundary conditions, and unhandled inputs.
Maintainability & consistency guidance: flags confusing naming, duplicated logic, anti-patterns, and deviations from project conventions; offers concrete refactors and style improvements.
Scalable reviews across scope: supports reviewing single files, modules, or entire projects, delivering prioritized issues with rationale and recommended fixes.

Quick Start

Provide the path to the file or set of files you want reviewed, and I will return a detailed, prioritized critique with concrete recommendations.

Frequently Asked Questions about bms:code-review

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

FAQPage Schema

How do I get constructive code reviews that identify edge-case handling and maintainability issues?▼

Constructive code reviews identify correctness, edge-case handling, and maintainability issues by analyzing single files, modules, or entire projects. The process emphasizes project conventions, tests, and readability, delivering prioritized issues with actionable remediation guidance and concrete refactors.

How do I review an entire project for consistency and maintainability issues?▼

You can review an entire project for maintainability and consistency by providing the path to the project files. The review scales across scopes, flagging confusing naming, duplicated logic, anti-patterns, and deviations from project conventions while delivering prioritized issues with clear rationale.

What is the best way to detect logic errors and unhandled boundary conditions in my code?▼

The best way to detect logic errors and unhandled boundary conditions is through a structured review process that analyzes correctness and edge-case handling. It highlights unhandled inputs and boundary conditions, offering actionable remediation guidance to elevate overall code quality.

Does automated code review work across multiple programming languages?▼

Automated code review works across multiple languages by analyzing code for correctness, maintainability, and project conventions. It evaluates readability and tests regardless of language, returning prioritized issues with concrete refactors and recommended fixes.

When should I not use a harsh code review approach?▼

You should not use a harsh code review approach when your team requires a softer feedback loop or when exploring experimental prototypes where immediate maintainability and strict convention adherence are not primary concerns.