Documentation

A complete walkthrough of CureBugs — from browsing your first challenge to publishing one that gets featured. Pick a topic on the left to dive in.

Getting Started

What is CureBugs?

A five-minute tour of the platform — what it is, what a challenge looks like, and how you get scored.

CureBugs is a debugging challenge platform built around real Go codebases. Instead of solving toy algorithm puzzles, you are dropped into a working project that has one deliberately planted bug, and your job is to find it, fix it, and explain why the bug existed.

Every challenge gives you three things:

  • A buggy Go project you can browse and edit in the browser
  • A problem statement written like a real bug report from a real team — symptoms, incident timeline, affected version, priority
  • A countdown timer that measures how quickly you can diagnose and patch the issue

You are scored by an AI evaluator across five dimensions, so the platform rewards not just finishing but how you got to the finish line.

The five scoring dimensions

DimensionWhat it measures
CorrectnessDid all the tests pass after your fix?
SpeedHow much of the time limit did you actually use?
Code QualityIs the fix idiomatic, minimal, and clean?
UnderstandingDoes your root-cause explanation match the actual defect?
AI Prompt QualityDid you use the AI assistant with sharp, targeted prompts?

Each dimension is worth up to 20 points, giving an overall score out of 100.

Two ways to use the platform

  1. Solve challenges — sharpen your debugging muscles, build a public profile, climb percentile ranks.
  2. Create challenges — publish your own bug hunts. Featured challenges appear on the public listing with your name attached, and every solve counts toward your creator stats.

Both paths are covered in this documentation. If this is your first visit, start with How to solve your first challenge below.

Still stuck? Browse the FAQ or jump straight to a challenge.