ck:code-review

Reviews code diffs, commits, PRs and full codebases for bugs and compliance with standards.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/duy-tung/claude-code-setup --skill ck-code-review-duy-tung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:code-review
Source: https://github.com/duy-tung/claude-code-setup/tree/main/claude/skills/ck-code-review
Command: npx skills add https://github.com/duy-tung/claude-code-setup --skill ck-code-review-duy-tung

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides an automated code review process with technical rigor, focusing on production risks, regression paths, and ensuring the implementation matches the requested change.

Core Features & Use Cases

  • Automated Code Review: Reviews diffs, PRs, commits, or full codebases for quality assurance.
  • Evidence-Based: Focuses on bugs, regressions, maintainability, reliability, and verification gaps.
  • Use Case: Imagine you need to review a PR with extensive changes. Use this Skill to automatically perform a comprehensive code review, identify issues, and verify the changes.

Quick Start

Use the ck:code-review skill to review all changes made in the last commit.

Frequently Asked Questions about ck:code-review

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

FAQPage Schema
How do I automate code review for a pull request with extensive changes?

Automate code review by analyzing source code diffs to identify bugs, security vulnerabilities, and compliance gaps with development standards. The process evaluates production risks and regression paths to ensure implementation matches requested changes.

What does an automated code review check for in a commit?

An automated code review checks commits for maintainability, reliability, and verification gaps. It assesses source code diffs for bugs, security vulnerabilities, and adherence to development specifications.

Can I review a full codebase for quality assurance or only individual diffs?

You can review a full codebase for quality assurance as well as individual diffs, pull requests, and commits. The review applies technical rigor to assess production risks and regression paths across the provided source code.

What is the best way to ensure code changes match requested specifications?

Ensure code changes match specifications by applying evidence-based code review guidelines to your source code diffs. This verifies the implementation matches the requested change while detecting bugs and security vulnerabilities.

Does automated code review work without writing automated testing scripts?

Automated code review operates independently of automated testing scripts by analyzing source code and diff comparisons directly. It identifies verification gaps and quality issues through evidence-based analysis rather than executing tests.

Why should I use automated code review instead of manual inspection for regressions?

Automated code review applies technical rigor to systematically detect regression paths and production risks that manual inspection might miss. It provides evidence-based assessment of bugs, security vulnerabilities, and development standard compliance.