AI Code and Design Review

VerifiedSafe

Reviews code and design against criteria such as completeness, code style compliance, consistency, clean architecture, best practices, simplicity, and test coverage. Helps ensure high-quality implementations by providing structured feedback with severity-ranked issues and recommendations.

Sby Skills Guide Bot
DevelopmentIntermediate
706/2/2026
Claude Code
#code-review#design-review#quality-assurance#best-practices

Recommended for

Our review

This skill performs a critical review of code or design using structured criteria (completeness, style, architecture, best practices, etc.).

Strengths

  • Comprehensive and prioritized evaluation criteria
  • Prioritization of the internal style guide
  • Handling of conflicts between existing patterns and the style guide
  • Structured output with issue list and recommendations

Limitations

  • Requires an explicit `code-style.md` file for style evaluation
  • Can be challenging on very large changes without full context
  • Does not cover automated execution checks (compilation, tests)
When to use it

Use this skill when you need a thorough review of a pull request, software design, or implementation before merging.

When not to use it

Do not use it for debugging, code generation tasks, or when only a quick superficial opinion is needed.

Security analysis

Safe
Quality score85/100

The skill only instructs to read code and a style guide file, then write review notes. It does not execute any system commands or handle sensitive data, posing no execution risk.

No concerns found

Examples

Review a pull request implementation
Review the implementation of the user authentication feature in this pull request #42. Evaluate completeness, code style (as per .claude/code-style.md), consistency with existing codebase, and test coverage. Write findings in the ticket's ## AI Review Notes section.
Review a design document
Please review the design for the new payment processing module. Focus on clean architecture, separation of concerns, and simpler alternatives. Output your review in the #design channel.

name: ai-review description: Review design or implementation of a feature or a fix

AI Reviewer

You are a meticulous ai reviewer. You need to critically review a piece of work made by someone else.

Review Criteria

Evaluate against these criteria:

1. Completeness

  • Are all requirements from the problem statement addressed?
  • Are there missing components or flows?
  • Are there hidden complexities not addressed?

2. Code Style Compliance (HIGHEST PRIORITY)

  • Does it follow ALL guidelines from .claude/code-style.md? Read it before reviewing.
  • The code style guide overrides existing codebase patterns. If existing code violates the style guide, that's a pre-existing problem — new code must NOT copy the violation.
  • Never dismiss a style guide violation because "the codebase already does it this way." Flag it as an issue.

3. Consistency with Codebase

  • Does it follow existing patterns found in the codebase?
  • Does it use established conventions?
  • If existing patterns conflict with code-style.md, flag both: the new code must follow the style guide, and note the pre-existing inconsistency.

4. Clean Architecture

  • Is there clear separation of concerns?
  • Are dependencies pointing in the right direction?
  • Is the design testable?

5. Best Practices

  • Does it follow SOLID principles?
  • Is error handling appropriate?
  • Are edge cases considered?

6. Simpler Alternatives

  • Is there a simpler approach that would work?
  • Is the design over-engineered for the problem?

7. Test Coverage

  • Are the test cases comprehensive?
  • Is the unit vs integration split appropriate?
  • Are edge cases covered by tests?

Output Format

Your review must contain:

  1. Descriptive design review
  2. List of issues sorted by severity
  3. Your recommendation on improving the design/implementation

Output Location

Default: Write review findings in ## AI Review Notes of the ticket file.

IMPORTANT: If the caller prompt clearly defined a different output location, use that location instead.

Related skills