ck:code-review

Analyze codebase changes for security vulnerabilities, compliance, and failure modes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need for rigorous code reviews, focusing on security, quality, and efficiency. It automates the review process, identifies potential issues, and promotes best practices.

Core Features & Use Cases

  • Adversarial Code Review: Actively attempts to break the code to uncover security holes and failure modes.
  • Input Modes: Supports reviewing PRs, commits, pending changes, full codebase scans, and parallel audits.
  • Technical Rigor: Ensures code quality by adhering to principles like YAGNI, KISS, and DRY.
  • Use Case: When preparing a PR for merge, use this Skill to automatically perform a full review, including spec compliance, code quality, and adversarial review.

Quick Start

Use the ck:code-review skill to review the latest changes in the 'main' branch.

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?

To perform an adversarial code review on a pull request, you need a tool that actively attempts to break the code to uncover security holes and failure modes. This Skill analyzes PR changes for vulnerabilities, technical compliance, and quality principles like YAGNI, KISS, and DRY.

What is the best way to automate security vulnerability scanning for pending code changes?

Automating security vulnerability scanning for pending changes requires analyzing the codebase against failure modes and compliance standards. This Skill reviews pending changes and commits through an adversarial process to identify security holes before merging.

Can I review full codebase changes in parallel for technical compliance?

Yes, you can review full codebase changes in parallel for technical compliance. The Skill supports parallel audits and full codebase scans to ensure code quality and security across the entire repository.

Do I need git and gh installed to automate code reviews?

Yes, you need git and gh installed along with a code-reviewer tool to automate code reviews. The Skill requires access to your codebase and these specific dependencies to analyze changes and perform adversarial audits.

Does automated code review work with commit history instead of pull requests?

Automated code review works with commit history in addition to pull requests. The Skill supports multiple input modes including commits, pending changes, and full codebase scans to identify security vulnerabilities and ensure technical rigor.

Why should I use adversarial review instead of standard code quality checks?

Adversarial review actively attempts to break the code to uncover hidden security vulnerabilities and failure modes, unlike standard checks. It enforces technical rigor by adhering to YAGNI, KISS, and DRY principles while ensuring spec compliance.