ck:code-review

Review code quality and verify correctness across multi-file features.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures code quality and technical rigor by providing thorough reviews, identifying edge cases, and verifying implementation against requirements, preventing bugs and improving maintainability.

Core Features & Use Cases

  • Technical Rigor: Enforces strict technical correctness and adherence to best practices (YAGNI, KISS, DRY).
  • Edge Case Scouting: Proactively identifies potential issues and boundary conditions before code review.
  • Task-Managed Pipeline: Orchestrates review, fix, and verification steps for complex changes.
  • Use Case: Before merging a new feature, use this Skill to perform a full codebase scan, identify potential bugs, and ensure all requirements are met, reducing the risk of production issues.

Quick Start

Use the ck:code-review skill to perform a full codebase scan and analysis.

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 a rigorous code review for a multi-file feature?

A rigorous code review evaluates multi-file features by scouting edge cases and verifying implementation against requirements using evidence-based claims. This enforces YAGNI, KISS, and DRY principles to prevent bugs and improve maintainability.

What is edge case scouting in software development?

Edge case scouting proactively identifies potential issues and boundary conditions before a code review. It ensures technical rigor by verifying implementation against requirements and preventing unhandled scenarios in software development.

How do I verify code correctness before merging a pull request?

Verify code correctness before merging by orchestrating review, fix, and verification cycles. This provides evidence-based feedback confirming all requirements are met and enforces strict technical standards to reduce production risks.

Does this code review tool enforce YAGNI, KISS, and DRY principles?

Yes, this enforces technical rigor by checking adherence to YAGNI, KISS, and DRY principles. It provides evidence-based claims and verifies code correctness before any completion claims or pull requests are made.

What's the best way to automate review and fix cycles for code quality?

Automate review and fix cycles by using a task-managed pipeline that handles review, fix, and verification steps for complex changes. This ensures technical correctness and reduces the risk of production issues.