workflow-review

Reviews GitHub issue diffs against acceptance criteria and publishes pass, changes_requested, or blocked verdicts.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill workflow-review-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-review
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/opencode/skills/workflow/workflow-review
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill workflow-review-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews on GitHub issues often miss uncommitted changes, accept stale verification evidence, or conflate baseline defects with introduced bugs. This Skill enforces an independent acceptance gate that inspects the actual committed and uncommitted diff before publishing a verdict. ## Core Features & Use Cases - Independent Diff Inspection: Identifies the exact base/head and full intended change including staged, unstaged, and untracked files, so no implementation is missed. - Acceptance Verification: Checks each acceptance row against real code, validates verification evidence freshness via source digests, and runs missing or discriminating tests. - Structured Verdict Publishing: Publishes Review records with stable finding IDs, severity, and file/line evidence via handoff.py, supporting pass, changes_requested, and blocked verdicts with re-review tracking. - Use Case: After a developer claims an issue is fixed, run /review on the issue to independently verify the diff against the acceptance contract, then publish a gated verdict with the exact next command (/execute or /commit). ## Quick Start Ask the agent to run /review on a GitHub issue URL to independently verify the implementation against its acceptance criteria and publish a verdict.

Frequently Asked Questions about workflow-review

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

FAQPage Schema
How do I review a GitHub issue implementation against acceptance criteria?

Run /review on the issue URL to load the handoff packet, inspect the full committed and uncommitted diff, check each acceptance row against actual code, and publish a pass, changes_requested, or blocked verdict with handoff.py.

How to verify code changes include uncommitted files in a review?

Identify the exact base/head and inspect committed diff plus staged, unstaged, and untracked files. This prevents missing implementation work when HEAD is unchanged but local modifications exist.

Can stale verification evidence be reused in a code review?

Check the evidence source digest against the current snapshot first. Reuse matching results, but run missing, stale, or discriminating tests rather than rerunning every command or accepting outdated evidence.

What happens when a re-review finds previous findings?

Re-reviews must carry every prior required finding ID as open, disputed, or resolved, with resolved IDs needing concrete evidence. Fetch the full previous review record and explicitly supersede it.

Why does a review verdict require a gate check before reporting readiness?

Passing schema and evidence validation alone cannot establish semantic correctness. Run handoff.py gate with the plan and review URLs, since a v1 pass label is not a v2 gated approval.