code-review

Identify code-quality and compliance issues in small changes before commit.

Updated Oct 26, 2025
One-click install
npx skills add https://github.com/discountedcookie/10x-mapmaster --skill code-review-discountedcookie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/discountedcookie/10x-mapmaster/tree/main/.opencode/skills/code-review
Command: npx skills add https://github.com/discountedcookie/10x-mapmaster --skill code-review-discountedcookie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs quick self-review of small changes, focusing on architecture, quality, and compliance.

Core Features & Use Cases

  • Architecture checks: Ensures database-first and security patterns are respected.
  • Quality checks: Type safety, tests, and naming conventions.
  • Non-fix orientation: Reports findings without applying changes.

Quick Start

Run a light review of small changes before committing, focusing on architecture and tests.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review code quality before committing changes?

Code review before commit identifies architecture, security, and quality issues in small changes without applying fixes. This Skill performs a quick sanity check on single-domain edits under ~100 lines, reporting findings to enforce compliance and test coverage before you push.

What types of code issues does a quality review catch?

Quality review catches architecture violations, security pattern breaches, type safety gaps, missing tests, naming convention issues, and style problems. This Skill applies database-first and security patterns, verifies test coverage, and structures findings in a report-only format.

When should I use a quick code review versus a full code review?

Use quick review for small, single-domain changes under ~100 lines—database-only or frontend-only edits—as a fast sanity check. For large, cross-domain, or security-sensitive changes, dispatch to a full code reviewer for deeper analysis.

Does code review work for large or complex changes?

This Skill is designed for small, focused changes in a single domain. For large, cross-domain, or security-critical modifications, use a full code-reviewer instead to handle complexity and risk appropriately.

Why report findings instead of automatically fixing code issues?

Reporting without fixing preserves your control over changes and ensures you understand each issue before resolution. This approach respects your intent and lets you decide whether and how to address each finding.