ck:code-review

Automate adversarial code review and quality assurance for codebases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github-api, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the process of code review and quality assurance, ensuring technical correctness and identifying potential issues before they become problems.

Core Features & Use Cases

  • Automated Code Review: Perform code reviews using adversarial methods to find security holes, false assumptions, and failure modes.
  • Input Modes: Supports PRs, commits, pending changes, codebase scans, and parallel codebase audits.
  • Use Case: Use this Skill to review a specific commit and identify potential security vulnerabilities or code quality issues.

Quick Start

Use the ck:code-review skill to review the latest 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 specific GitHub commit?

To automate code review for a specific commit, you can use a skill that fetches commit data via the GitHub API and performs adversarial analysis to identify security holes and code quality issues. It requires git and GitHub API access to extract the necessary codebase information.

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

Adversarial code review is an automated technique that aggressively tests codebase assumptions to uncover failure modes and security vulnerabilities. By simulating edge cases and attacking false assumptions, it identifies potential issues before they manifest in production environments.

Do I need git and GitHub API access to run automated code quality assurance?

Yes, you need both git and GitHub API access to run automated code quality assurance. These dependencies are required to fetch code changes, pull request details, and commit information necessary for performing accurate reviews and identifying potential issues.

Can I scan an entire codebase for potential failure modes and false assumptions?

Yes, you can scan an entire codebase for potential failure modes. The automated review process supports multiple input modes including codebase scans and parallel codebase audits to comprehensively identify security holes and false assumptions across your project.

What's the best way to review pending code changes for technical correctness?

The best way to review pending code changes for technical correctness is using an automated quality assurance skill that supports pending changes as an input mode. It performs adversarial reviews to ensure technical correctness and identifies potential issues automatically.