ck:code-review

Review code quality with edge-case scouting and verification gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers often merge or claim completion without thorough code review, leading to hidden bugs, edge‑case failures, and unverified claims. This Skill enforces rigorous, evidence‑based review to catch issues early.

Core Features & Use Cases

  • Guided Review Process: Offers default operations for recent changes, full codebase scans, or parallel multi‑reviewer audits.
  • Edge‑Case Scouting: Runs a scouting step to identify hidden side effects before formal review.
  • Task‑Managed Pipelines: Creates Claude native tasks to chain scouting, review, fixing, and verification automatically.
  • Verification Gates: Requires test passes, build success, and evidence before any completion claim.
  • Integration Hooks: Works with Git workflows, PR pipelines, and sub‑agent orchestration.

Quick Start

Ask the code‑review skill to review the recent changes in the repository.

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 a rigorous code review on recent pull request changes?

Edge-case scouting identifies hidden side effects and unhandled scenarios before formal code review begins. It runs a dedicated scouting step to detect potential failures in recent pull request changes or full codebase scans, ensuring technical correctness and preventing unverified claims.

Can I automate code review and fixing using task pipelines?

Yes, you can automate code review and fixing using Claude native task pipelines. The skill chains scouting, review, fixing, and verification automatically, creating a managed workflow that requires test passes and build success before validating completion claims.

Does this code review skill support parallel multi-reviewer audits?

Verification gates require test passes, build success, and concrete evidence before allowing any completion claim. This prevents developers from merging code with hidden bugs or edge-case failures by enforcing evidence-based validation at the end of the task pipeline.

What's the best way to enforce software quality principles during a codebase scan?

The best way to enforce software quality during a codebase scan is applying YAGNI, KISS, and DRY principles alongside automated edge-case scouting. This combination catches hidden side effects, validates technical correctness, and ensures no unverified completion claims slip through.

When do I need edge-case scouting for my code review process?

You need edge-case scouting for your code review process when merging changes without thorough verification risks hidden bugs. It is essential before formal review to identify hidden side effects, validate technical correctness, and prevent unverified claims in pull request workflows.