ck:code-review

Identify security holes and failure modes via adversarial code review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Adversarial, evidence-based code reviews identify security holes, false assumptions, and failure modes across input modes (pending changes, PRs, commits, or full codebase scans).

Core Features & Use Cases

  • Adversarial red-team style code review that actively tries to break the code.
  • Supports input modes: PR, commit, pending changes, codebase scan.
  • Produces evidence-backed findings and verification.
  • Provides structured outputs with severity, category, and location to guide fixes.

Quick Start

Invoke /ck:code-review with your target (PR number, commit hash, or codebase) to start an adversarial 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 perform an adversarial code review on a pull request?

Adversarial code review actively tries to break code by identifying security holes and false assumptions. Invoke the review targeting a PR number to receive evidence-backed findings with severity, category, and location to guide fixes.

What is red-team code review and how does it find failure modes?

Red-team code review is an adversarial technique that actively hunts for security holes and false assumptions. It produces structured, evidence-based results detailing severity, category, and location to guide remediation across pending changes or full codebases.

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

Yes, you can scan a full codebase to find security holes and false assumptions. The review supports full codebase scans alongside PR diffs and commit histories, delivering structured findings with severity and location for remediation.

How do I verify security findings during a code review?

Verify security findings by using evidence-based adversarial code reviews. The process outputs structured results containing severity, category, location, and recommended fixes, ensuring findings are grounded in evidence rather than assumptions.

Does diff analysis work with commit histories and pending changes?

Diff analysis works with commit histories and pending changes. The review accepts PRs, commit hashes, and pending changes as input modes to perform adversarial analysis and output structured remediation guidance.