Beat the Reviewer

1. Make your own copy of the template. Public, if you want to appear on the board.
2. Read a level's RULE.md, then branch as level-01 … level-10 — you are told exactly what gets a request refused, never what gets it through.
3. Open a pull request. Your request goes in the pull request body.
4. The reviewer replies in under a minute. Refused? Edit the body and it judges again.

cat levels/01/RULE.md

git checkout -b level-01 main
echo "my attempt" > attempts/01.md
git add . && git commit -m "level 01"
git push -u origin level-01

gh pr create --base main --title "level 01" \
  --body "your request here"

Levels unlock in order. No API key, nothing to configure.

Solve it yourself. Using an AI to write your requests is not allowed.

Use one to think if you like — to explain a concept, or say what an argument rests on. Having it draft the request is solving the puzzle, and the puzzle is the point.

Nothing is judged on how it is written. What ends a run is conduct: a level won within 60 seconds of opening the pull request, four levels with no refusal at any of them, wins less than 90 seconds apart, or reusing a request that has already won. You are always told which rule and the numbers behind it.