code-review

Analyze code diffs for bugs, security vulnerabilities, and correctness issues.

399|31|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/tobihagemann/turbo --skill code-review-tobihagemann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/tobihagemann/turbo/tree/main/skills/code-review
Command: npx skills add https://github.com/tobihagemann/turbo --skill code-review-tobihagemann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of identifying bugs, security vulnerabilities, and correctness issues within code changes, ensuring higher quality and more secure software.

Core Features & Use Cases

  • Automated Code Analysis: Analyzes diffs against strict criteria for bugs and security flaws.
  • Structured Findings: Returns clear, prioritized findings with explanations and severity levels.
  • Use Case: Before merging a pull request, use this Skill to perform a thorough code review, flagging potential issues that human reviewers might miss.

Quick Start

Run a code review on my uncommitted changes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I analyze uncommitted changes for bugs and security vulnerabilities?

You can analyze uncommitted changes by providing them as context to an automated code review. The tool identifies introduced bugs and security flaws, categorizing findings by priority with explanations.

How does automated code review detect security issues in a specific commit?

Automated code review detects security issues by analyzing the diff of a specific commit SHA against strict determination criteria. It flags potential vulnerabilities and correctness problems introduced in that changeset.

Can I use this to check code quality before merging a pull request?

Yes, you can check code quality before merging a pull request by running an automated diff analysis. It performs a thorough scan to flag potential bugs and security issues that human reviewers might miss.

What context is required to scan a code changeset for correctness issues?

To scan a code changeset for correctness issues, you must provide context such as uncommitted changes, a base branch, or a specific commit SHA. The analysis targets issues introduced within that specific changeset.

What is the best way to get structured findings for detected bugs in code?

The best way to get structured findings for detected bugs is through automated diff analysis. It returns prioritized results complete with severity levels and explanations for each identified issue.

Does this code review tool work with any specific base branch?

Yes, the code review tool works by analyzing diffs against a specified base branch. It uses strict criteria to identify and categorize any bugs or security vulnerabilities introduced relative to that branch.