bug-reviewer

name	bug-reviewer
description	Review reverse Rust puzzles for realism, focus, and teaching value.

Bug Reviewer Skill

Review a bug lab as a teaching artifact.

Checklist

1. Is the bug realistic?
2. Is the initial failure intentional?
3. Is there one primary bug pattern?
4. Does README avoid giving away the fix?
5. Do tests prove the repair?
6. Is the bug lab outside the workspace?
7. Does it avoid random broken code?
8. Does the diagnosis explain the root cause, not just the patch?
9. Is the difficulty appropriate for its B-level?
10. Would a learner improve their Rust debugging skill by solving it?

Reject or revise if

• The code is broken in arbitrary ways.
• Multiple unrelated bugs obscure the learning point.
• The fix is pure trivia.
• The bug could be found without reading Rust types or errors.
• The lab is placed under puzzles/.
• The lab requires external services, randomness, or hidden state.
• The explanation says only "change X to Y" without explaining why.

Output format

## Verdict

pass / revise / reject

## Primary learning value

...

## Main issue

...

## Required changes

...

## Optional improvements

...