Skill

devflow-reviewing

Use when the active DevFlow flow is in 'review' state. Guides self-review via diff analysis and writes the agent summary + testing instructions.

Install

npx claudepluginhub klausfreiberufler/devflow-mcp --plugin devflow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

The flow is `review`. The agent has submitted work; you are checking it and preparing handover notes for the user.

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

166.1k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

166.1k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

166.1k

Stats

Stars1

Forks0

Last CommitApr 17, 2026

Actions

View Source View Plugin View on GitHub View README

DevFlow — Review State

The flow is review. The agent has submitted work; you are checking it and preparing handover notes for the user.

Superpowers Integration

If superpowers:code-review is available, use it for the diff analysis. Otherwise, do an inline self-review following the steps below.

Inline Self-Review (fallback)

Run git diff <base-branch>...HEAD to see everything this flow added

For each changed file:

Does the change match the approved plan?
Any obvious bugs, missing error paths, leftover debug code?
Test coverage adequate?
Follows project conventions (look at neighbouring files)?

Check acceptance criteria from the flow — each one ticked off?

Fix findings with additional commits on the same branch

Before Marking Done

The review → done transition is human-only in strict mode — you cannot do it. Your job stops at:

✅ Clean self-review complete

✅ agentSummary populated via flow_update

✅ testingInstructions populated via flow_update

✅ Docs updated if applicable

Then wait. The user tests in DevFlow UI and clicks approve (or rejects back to in_progress with feedback).

On Reject

If the flow is rejected back to in_progress, call devflow_init again — the MCP response will include previousFeedback. Address it before retrying review.

DevFlow — Review State

The flow is review. The agent has submitted work; you are checking it and preparing handover notes for the user.

Superpowers Integration

If superpowers:code-review is available, use it for the diff analysis. Otherwise, do an inline self-review following the steps below.

Inline Self-Review (fallback)

Run git diff <base-branch>...HEAD to see everything this flow added
For each changed file:
- Does the change match the approved plan?
- Any obvious bugs, missing error paths, leftover debug code?
- Test coverage adequate?
- Follows project conventions (look at neighbouring files)?
Check acceptance criteria from the flow — each one ticked off?
Fix findings with additional commits on the same branch

Before Marking Done

The review → done transition is human-only in strict mode — you cannot do it. Your job stops at:

✅ Clean self-review complete
✅ agentSummary populated via flow_update
✅ testingInstructions populated via flow_update
✅ Docs updated if applicable

Then wait. The user tests in DevFlow UI and clicks approve (or rejects back to in_progress with feedback).

On Reject

If the flow is rejected back to in_progress, call devflow_init again — the MCP response will include previousFeedback. Address it before retrying review.