code-review

Review code line-by-line to identify and fix bugs and logic errors.

1|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/blink-new/claude --skill code-review-blink-new
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/blink-new/claude/tree/main/skills/code-review
Command: npx skills add https://github.com/blink-new/claude --skill code-review-blink-new

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the critical need for thorough code quality assurance by identifying and rectifying all bugs, logic errors, and redundancies in code.

Core Features & Use Cases

  • Comprehensive Auditing: Performs deep, line-by-line analysis of code to uncover hidden issues.
  • Bug Resolution: Automatically fixes all identified bugs and refactors code for clarity and efficiency.
  • Verification: Ensures code is 100% functional and free of errors through rigorous checks.
  • Use Case: Reviewing a new feature implementation before merging a pull request to guarantee stability and adherence to coding standards.

Quick Start

Perform a deep code review on the provided feature, fixing all bugs and ensuring 100% correctness.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I conduct a thorough code review to find hidden bugs before a pull request?

A thorough code review finds hidden bugs by performing line-by-line analysis to identify logic errors, redundancies, and issues, ensuring your pull request is stable and 100% functional before merging.

What is the best way to audit code changes for logic errors and redundancies?

Auditing code changes for logic errors involves tracing the call stack and verifying functionality to uncover redundancies, which guarantees clean code and adherence to quality assurance standards.

Can I automatically fix bugs and refactor code during a review?

Yes, you can automatically fix bugs and refactor code during a review by identifying issues and rectifying them, which resolves errors and improves code clarity and operational efficiency.

Does line-by-line code review work for verifying features across an entire codebase?

Line-by-line code review works for verifying features across a codebase by tracing call stacks and conducting deep analysis to ensure 100% functionality and eliminate hidden errors.

When do I need to trace a call stack to verify code functionality?

You need to trace a call stack to verify code functionality when auditing complex features, ensuring that logic flows correctly and identifying exactly where bugs or redundancies occur.