ck:code-review

Name: ck:code-review
Availability: InStock
Author: EdgeHunt

Identify weaknesses in code changes through adversarial, evidence-based reviews.

Updated Apr 2, 2026

Search Tags:#verification #edge-cases #code-review #adversarial #diff-analysis #security-testing

Ready to run

npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-code-review-edgehunt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ck:code-review
Source: https://github.com/EdgeHunt/EdgeHunt/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/EdgeHunt/EdgeHunt --skill ck-code-review-edgehunt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Adversarial code review identifies weaknesses in changes, providing evidence-based critiques that go beyond surface-level style checks.

Core Features & Use Cases

Supports input modes: pending changes, PR number/URL, commit hash, and codebase scan.
Always-on red-team analysis actively tries to break the code, uncovering security holes, false assumptions, and failure modes.
Provides structured findings with evidence and a clear verification path before merge.

Quick Start

Provide the target (PR, commit, pending changes, or codebase) and request an adversarial, evidence-driven code review.

Frequently Asked Questions about ck:code-review

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

FAQPage Schema

How do I run an adversarial code review on a PR diff?▼

To run an adversarial code review on a PR diff, provide the PR number or URL to trigger an evidence-based analysis that actively tries to break the code changes and uncover security holes.

What is red-team analysis for code changes?▼

Red-team analysis for code changes is an adversarial review method that actively probes diffs to uncover security holes, false assumptions, and failure modes, providing structured findings with evidence before merge.

Does adversarial code review work with pending changes and commit hashes?▼

Yes, adversarial code review works with pending changes and commit hashes, supporting multiple input modes including PR number, URL, commit hash, and full codebase scans to identify weaknesses.

How do I verify code changes before a merge?▼

You verify code changes before a merge by requesting an evidence-driven review that applies formal verification gates and documents structured findings, ensuring a clear verification path is satisfied.

Can I scan a full codebase for security weaknesses and false assumptions?▼

Yes, you can scan a full codebase for security weaknesses and false assumptions by selecting the codebase scan input mode, which applies rigorous red-team thinking to uncover hidden failure modes.