Every Monday a new challenge is published: a short, realistic editing task with a vimbot score to beat and its own leaderboard. Sign in to play.
Recent challenges
Cache Me If You Can (2026-10-26): Nobody remembers which backup hosts were retired, and the nightly job still dutifully tries all of them. The vimbot solved it in 40 keystrokes.
Frost Bite (2026-10-19): The sprint ended on Friday, the checklist did not, and the changelog now disagrees with its own history. The vimbot solved it in 148 keystrokes.
Errand Boy (2026-10-12): Friday afternoon, and this week's list has been quietly growing while its owner stayed optimistic. The vimbot solved it in 80 keystrokes.
Ship Shape (2026-10-05): The site reliability lead scheduled tonight's cluster deploy with the staging flags still intact. The vimbot solved it in 51 keystrokes.
Staging Fright (2026-09-28): The backend lead cloned the staging environment for production and went to lunch right before cutover. The vimbot solved it in 64 keystrokes.
Token Gesture (2026-09-21): The security team refactored the token schema and the test suite has not compiled since lunch. The vimbot solved it in 37 keystrokes.
Scope Creep (2026-09-14): Someone promoted the staging gateway by hand and the compliance audit begins in twenty minutes. The vimbot solved it in 34 keystrokes.
Commit Issues (2026-09-07): The release engineer rejected the hotfix notes and the deployment window closes in ten minutes. The vimbot solved it in 32 keystrokes.
Shift Work (2026-08-31): The platform lead shifted the topology diagram by three columns and left for the weekend. The vimbot solved it in 24 keystrokes.
Pipe Down (2026-08-30): The intern pasted a raw terminal dump into the incident ticket right before the postmortem meeting. The vimbot solved it in 45 keystrokes.
Box Cutter (2026-08-24): The lead engineer approved the migration checklist without noticing the typos in the YAML block. The vimbot solved it in 25 keystrokes.
Patch Work (2026-08-23): The release build tagged successfully but the changelog looks like a hasty Friday afternoon job. The vimbot solved it in 71 keystrokes.