code-review

Review branch diffs and produce a severity-tagged findings table.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents defective or insecure code from being pushed by systematically reviewing branch changes for logic errors, security holes, performance regressions, and architecture inconsistencies before merge.

Core Features & Use Cases

  • Diff scope analysis: Inspect commit range and file-level diffs to focus review effort and estimate scope.
  • Issue classification: Identify logic bugs, unhandled exceptions, security risks (for example SQL injection or hardcoded secrets), performance hotspots, and violations of project architecture.
  • Actionable reporting: Produce a severity-tagged findings table with file references, problem descriptions, and suggested fixes; escalate High issues for immediate remediation.
  • Use Case: Run this workflow prior to opening a pull request or pushing a feature branch to catch regressions and prevent security incidents.

Quick Start

Run the code-review skill to analyze the current branch diffs against the base branch and produce a severity-tagged table of issues with recommended fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review git diffs for security and performance issues before a pull request?

Reviewing git diffs for security and performance issues involves inspecting commit ranges and file-level changes to identify logic bugs, security holes, and performance regressions before pushing a feature branch.

What is the best way to catch logic bugs and hardcoded secrets in branch diffs?

The best way to catch logic bugs and hardcoded secrets in branch diffs is to classify issues by category, producing a severity-tagged findings table with file references and recommended fixes to escalate high-priority risks.

How do I check branch changes against the base branch for architecture violations?

Checking branch changes against the base branch for architecture violations requires analyzing file-level diffs to detect inconsistencies with project architecture across frontend, backend, and infra code.

Can I automatically fix code review findings in my commit range?

You can automatically fix code review findings by prompting the review workflow to apply suggested fixes for identified issues, while high-severity problems may require explicit developer action for remediation.

Does automated code review work with frontend, backend, and infra code?

Automated code review works across frontend, backend, and infra code by analyzing file-level diffs against the base branch to detect unhandled exceptions, SQL injection risks, and performance hotspots.

When do I need a severity-tagged findings table for my pull request?

You need a severity-tagged findings table for your pull request when preparing a feature branch for merge, ensuring that high-severity issues are escalated for immediate remediation before integration.