ck:code-review

Scout edge cases and review code before merges or PR approvals.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often fail to catch edge cases and ensure rigorous verification before merging. This skill guides subagents to scout edge cases, perform thorough reviews, and enforce evidence-based completion.

Core Features & Use Cases

  • Scout edge cases for multi-file features and complex refactors.
  • Dispatch parallel code-reviewer subagents to verify issues across scopes.
  • Enforce verification gates and task-based review pipelines before completion.

Quick Start

Initiate a scout to identify edge cases, then run a code-review, followed by a fix and verify cycle as needed.

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 to catch edge cases before merging?

Rigorous code review uses a scout–review–fix–verify workflow to catch edge cases before merging. It initiates a scout to identify edge cases, runs thorough code reviews, and enforces verification gates to ensure changes meet quality standards.

How do I verify multi-file features and complex refactors during a code review?

To verify multi-file features and complex refactors, dispatch parallel code-reviewer subagents to check issues across different scopes. This parallel review process ensures comprehensive coverage and enforces evidence-based completion before task pipelines finish.

What is the best way to enforce quality standards for PR approvals?

Enforcing quality standards for PR approvals requires task-based review pipelines with explicit error handling. You apply an evidence-based completion gate to verify that all identified edge cases are resolved before approving the pull request.

Can I use parallel reviews to verify issues across multiple code scopes?

Yes, parallel reviews can verify issues across multiple code scopes. The process dispatches parallel code-reviewer subagents to simultaneously evaluate different parts of multi-file features, ensuring thorough verification and faster issue scouting.

Does evidence-based completion work for complex refactors and edge-case scouting?

Evidence-based completion works effectively for complex refactors and edge-case scouting by enforcing verification gates. It requires explicit proof that all edge cases are scouted, reviewed, fixed, and verified before completing the code review pipeline.