code-review

Audit Opus 4.5 code against a 100-point rubric across five categories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sihu-dev/bidflow --skill code-review-sihu-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/sihu-dev/bidflow/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/sihu-dev/bidflow --skill code-review-sihu-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manual code reviews are slow and prone to missing issues. This Skill automates code quality checks across multiple dimensions including quality, security, performance, UI, and tests.

Core Features & Use Cases

  • Quality & Security Audits: Checks TypeScript strictness, naming, security vulnerabilities, and more.
  • Performance & UI Review: Identifies performance bottlenecks and UI concerns.
  • Use Case: A developer submits a PR and receives a structured 100-point review with actionable notes.

Quick Start

Use the /review command to start a code review, e.g., /review --focus security or /review path/to/file.tsx

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code reviews across quality, security, and performance?

Automated code reviews assess code quality, security vulnerabilities, performance bottlenecks, and UI/UX compliance using a 100-point rubric across five dimensions. This Skill evaluates TypeScript strictness, naming conventions, hard-coded secrets, injection risks, render optimization, and test coverage during PR merge and pre-commit phases, eliminating manual review delays.

What does a code review check for in TypeScript projects?

Code reviews verify TypeScript strict mode compliance, functional programming patterns, single-responsibility principle adherence, and naming conventions. Security checks detect hard-coded secrets and injection vulnerabilities; performance audits flag unnecessary re-renders and N+1 queries; UI checks enforce monochrome design system compliance and responsive layouts.

Can I run code reviews on specific files or focus on particular domains?

Yes, use the /review command with options like /review --focus security or /review path/to/file.tsx to target specific files or audit dimensions. This allows focused reviews on security, performance, UI, quality, or testing concerns rather than full-scope analysis.

When should I run automated code reviews in my development workflow?

Apply automated code reviews during code completion, pre-commit validation, and PR merge gates. This catches issues early in development and prevents quality, security, and performance problems from reaching production without manual reviewer delays.

What are the limitations of automated code reviews versus manual review?

Automated reviews excel at detecting structural violations, security patterns, and performance anti-patterns against a defined rubric. However, they assess codebases matching the Opus 4.5 tech stack (TypeScript, monochrome design system, functional patterns) and cannot replace human judgment on architecture, business logic, or context-specific trade-offs.