rubber-duck

Critique plans, code, and tests with structured CRITICAL, WARN, and INFO verdicts.

23|7|Updated Feb 14, 2026

Search Tags:#review #diff #code-review #plan-review #rubber-duck #test-review

Ready to run

npx skills add https://github.com/kinncj/MAPLE --skill rubber-duck-kinncj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rubber-duck
Source: https://github.com/kinncj/MAPLE/tree/main/template/.opencode/skills/rubber-duck
Command: npx skills add https://github.com/kinncj/MAPLE --skill rubber-duck-kinncj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an independent second opinion on plans, implementations, or test suites, helping teams catch issues that the primary reviewer may miss and improving overall quality.

Core Features & Use Cases

Independent critique for plans, code, and tests to surface critical insights.
Structured verdicts including CRITICAL, WARN, and INFO with actionable recommendations (APPROVE/REQUEST_CHANGES).
Versatile review modes: PLAN REVIEW, CODE REVIEW, and TEST REVIEW to fit different project stages.

Quick Start

Invoke the rubber-duck at the appropriate checkpoint to receive a focused critique.

Frequently Asked Questions about rubber-duck

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I get an independent code review to surface critical gaps in my diff?▼

An independent code review surfaces critical gaps in your diff by applying a structured critique across multi-file changes, returning a verdict with CRITICAL, WARN, and INFO outputs to flag risks before merging.

What is a plan review and when do I need it for my software project?▼

A plan review provides an independent critique of your project plans to surface critical insights and risks. You need it before implementation begins to identify gaps and receive an actionable APPROVE or REQUEST_CHANGES verdict.

Can I use an automated test review to catch risks in my test suites?▼

Yes, an automated test review applies an independent critique to your test suites to surface gaps and risks. It returns a structured verdict with CRITICAL, WARN, and INFO outputs to improve overall test quality.

What's the best way to structure feedback from an independent critique of plans or code?▼

The best way to structure feedback from an independent critique is using a verdict format with CRITICAL, WARN, and INFO outputs, culminating in an actionable APPROVE or REQUEST_CHANGES recommendation for clear decision-making.

Does the rubber-duck review approach work on multi-file changes or only single files?▼

The rubber-duck review approach works across multi-file changes, applying an independent critique to surface gaps and risks in complex implementations, plans, and test suites to improve overall quality.