ck:code-review

Automate code review for spec compliance, quality, and adversarial analysis.

1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/TNHoang2708/Gym_Ver2 --skill ck-code-review-tnhoang2708
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:code-review
Source: https://github.com/TNHoang2708/Gym_Ver2/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/TNHoang2708/Gym_Ver2 --skill ck-code-review-tnhoang2708

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates code reviews with adversarial rigor, ensuring technical correctness and security. It supports various input modes for code analysis and provides detailed feedback.

Core Features & Use Cases

  • Adversarial Code Review: Identifies security holes, false assumptions, and failure modes.
  • Input Modes: Supports PRs, commits, pending changes, codebase scans, and parallel reviews.
  • Use Case: Use this Skill to review a specific PR or commit, or perform a full codebase scan for potential issues.

Quick Start

Use the ck:code-review skill to review the PR with number #123.

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 GitHub pull request?

Automated code review for a GitHub pull request is performed by analyzing code changes fetched via the GitHub API. It checks spec compliance, code quality, and security to ensure technical correctness.

What is adversarial code review and how does it find security holes?

Adversarial code review is an analysis technique that aggressively identifies security holes, false assumptions, and failure modes. It evaluates robustness by actively probing code for potential exploitation paths.

Can I scan my full codebase for potential security issues?

Full codebase scans are supported to detect potential security issues and technical vulnerabilities. This mode analyzes the entire repository rather than isolated commits or pull requests.

Do I need GitHub API access to run automated code analysis?

GitHub API access and Git commands are required to fetch and analyze code changes. These dependencies allow the review process to pull diffs, commits, and pending changes for evaluation.

What types of code changes can be analyzed besides pull requests?

Analysis supports various input modes including individual commits, pending local changes, and full codebase scans. Parallel reviews can also be executed to handle multiple change sets concurrently.