puzzle-reviewer

name	puzzle-reviewer
description	Review Rust puzzles for quality, correctness, and learning value.

Puzzle Reviewer Skill

Review a puzzle as a learning artifact for an experienced programmer learning Rust.

Checklist

Check the following:

1. Does the puzzle teach a Rust-specific concept?
2. Is the API small and explicit?
3. Does src/lib.rs compile as starter code?
4. Do tests cover happy paths and edge cases?
5. Does README explain the goal without giving away the solution?
6. Are the constraints precise enough to avoid guessing?
7. Are failures educational?
8. Does Puzzle.toml contain correct level, track, topics, and estimate?
9. Does the puzzle avoid unnecessary dependencies?
10. Is the puzzle too trivial for its level?

Reject or revise if

• The main task is generic programming basics.
• It could be solved without confronting a Rust concept.
• It is a LeetCode clone with no Rust-specific API design.
• Tests depend on randomness, time, network, or machine-specific behavior.
• README reveals the complete solution.
• The starter code does not compile by accident.

Output format

Use this format when reviewing:

## Verdict

pass / revise / reject

## Main issue

...

## Required changes

...

## Optional improvements

...