code-reviewer

Review code changes across six dimensions with BLOCKING-first findings.

Updated Jul 18, 2025
One-click install
npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill code-reviewer-dougborg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/dougborg/stocktrim-openapi-client/tree/main/.claude/skills/code-reviewer
Command: npx skills add https://github.com/dougborg/stocktrim-openapi-client --skill code-reviewer-dougborg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams prevent bugs, regressions, and vulnerabilities by performing a structured, dimension-based code review that leads to clear approve/request-changes decisions.

Core Features & Use Cases

  • 6-Dimensional Reviews: Evaluates correctness, design, readability, performance, testing, and security using dedicated checklists.
  • Risk-First Classification: Labels findings as BLOCKING, SUGGESTION, or NITPICK to prioritize what must be fixed before merge.
  • Developer Workflow Fit: Works with PR context or locally available diffs (e.g., via git diff) and can guide reviews whether or not a separate code-reviewer agent is available.
  • Non-Redundant Feedback: Avoids duplicating linter/typechecker findings and focuses on actionable human context.

Quick Start

Use the code-reviewer skill to review the changes in the current branch and produce a structured report grouped by the six dimensions, with BLOCKING items listed first.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
What is a structured code review and how does it prevent merge defects?

A structured code review evaluates git diffs across correctness, design, readability, performance, testing, and security dimensions to reduce defects and risk before merge, yielding categorized findings that prioritize BLOCKING issues.

How do I review a git diff for correctness and security before merging?

Apply a dimensional checklist to the git diff to assess correctness, architecture, and security, producing a risk-first report that labels findings as BLOCKING, SUGGESTION, or NITPICK to guide merge approval decisions.

Does code review security analysis replace linter and typechecker checks?

No, structured code review intentionally avoids duplicating linter and typechecker findings, focusing instead on actionable human context like design flaws, security vulnerabilities, and missing test coverage in the PR diff.

Can I use automated code review on targeted file changes instead of full PRs?

Yes, dimensional code review applies to both PR context and locally available diffs, using git diff-based context gathering to evaluate targeted file changes and generate categorized reports before merge.

What's the best way to prioritize code review findings for a merge request?

Use a risk-first classification that labels findings as BLOCKING, SUGGESTION, or NITPICK, ensuring security issues are treated as non-negotiable and BLOCKING items are listed first to prioritize merge fixes.

How does dimensional code review handle performance and testing evaluation?

Dimensional code review applies dedicated checklists for performance and testing to the git diff, identifying regressions and missing coverage while categorizing findings by severity to reduce pre-merge risk.