Skill

adhoc-review

Use when you want a code review on recent changes, a specific file, or a pull request — 'review this', 'check my code', 'what did I miss'. Works in any project without setup.

From dp-cto

Install

Run in your terminal

npx claudepluginhub raisedadead/dotplugins --plugin dp-cto

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

ecc

145.8k

agent-introspection-debugging

Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.

ecc

145.8k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

ecc

145.8k

Stats

Parent Repo Stars3

Parent Repo Forks0

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Step 2: Select Lens

Present a lens menu via AskUserQuestion:

Quick — single lens, fast pass (pick the most relevant)

Full — security + simplification lenses in parallel

Sweep — drift detection (dead code, stale comments, naming)

Pushback — challenge a proposal or plan

If the user provided a lens in their args (e.g., /dp-cto:adhoc-review security), skip the menu.

Step 3: Dispatch Reviewer

Spawn reviewer agent(s) via Agent tool with subagent_type: "dp-cto:reviewer".

For Quick: 1 agent with the selected lens. For Full: 2 agents in parallel (primary lens + adversarial lens). For Sweep: 1 sweeper agent instead. For Pushback: 1 agent with pushback lens.

Include in the prompt:

The file scope or diff from Step 1

The selected lens

"This is an ad-hoc review — no beads, no task_id, no stage context."

Ad-Hoc Code Review

Standalone code review skill. Works in any project without beads or an active dp-cto epic. Bypasses stage enforcement via the adhoc-* prefix.

Step 1: Detect Scope

Determine what to review:

If args specify files or directories → use those
If git diff --name-only HEAD~1 has changes → use the diff
Otherwise → ask: "What should I review? Provide file paths, a git range, or 'all' for the full project."

Step 2: Select Lens

Present a lens menu via AskUserQuestion:

Quick — single lens, fast pass (pick the most relevant)
Full — security + simplification lenses in parallel
Sweep — drift detection (dead code, stale comments, naming)
Pushback — challenge a proposal or plan

If the user provided a lens in their args (e.g., /dp-cto:adhoc-review security), skip the menu.

Step 3: Dispatch Reviewer

Spawn reviewer agent(s) via Agent tool with subagent_type: "dp-cto:reviewer".

Include in the prompt:

The file scope or diff from Step 1
The selected lens
"This is an ad-hoc review — no beads, no task_id, no stage context."

Step 4: Consolidate and Present

Parse agent receipt(s). Present findings grouped by severity:

CRITICAL — must address
WARNING — should address
SUGGESTION — optional

If multiple agents ran, deduplicate by file:line (keep higher severity).

No Beads Required

This skill operates without beads. No epic, no task tracking, no stage transitions. The adhoc-* prefix ensures the skill-gate hook passes it through at any stage.