Frequently Asked Questions

What is PR Dojo?

PR Dojo is a practice platform for developers to improve their code review skills. We present you with buggy code from real rejected pull requests, and challenge you to find the issues and write fixes.

Is PR Dojo free to use?

Yes, PR Dojo is completely free. All challenges are available without any cost or subscription. We believe in making code review practice accessible to everyone.

How do I start?

Head to the Challenges page and pick a challenge that matches your skill level. Each challenge shows its difficulty rating, XP value, and the type of bug you'll be looking for.

How are challenges scored?

Each challenge awards XP based on its difficulty (1-5 stars). You earn the full amount when your submitted fix correctly resolves all identified issues. Partial credit may be awarded for fixing some but not all bugs.

What if I get stuck?

Every challenge provides hints that reveal line-by-line descriptions of the issues. Hints are designed to guide you without giving away the full solution — use them when you need a nudge in the right direction.

Can I submit my own challenges?

Not yet, but it's on our roadmap. We're planning to add a contribution system where experienced developers can submit their own rejected PRs as practice challenges. Stay tuned!

What programming languages are supported?

Currently we focus on TypeScript and JavaScript, as these are the most common languages in the PRs we curate. We plan to expand to other languages like Python, Go, and Rust as the platform grows.

How does the XP system work?

XP (experience points) are awarded when you successfully submit a fix for a challenge. Higher difficulty challenges award more XP. Your XP total contributes to your rank and is displayed on your profile.

Can I use PR Dojo for team training?

Absolutely. Many teams use PR Dojo to practice code review as a group activity. While individual profiles are currently supported, we're planning team features like shared leaderboards and team challenges.

Where do the challenges come from?

Our challenges are sourced from real rejected pull requests across open-source projects (with permission and anonymization). We strip away sensitive information and focus purely on the code issues to create safe learning environments.