Hello CF,↵
↵
If you've ever wasted contest time copy-pasting samples into an online compiler or fighting with IDE extensy Codeforces,↵
↵
During contests, I kept losing time on things that had nothing to do with solving the problem — manually copying samples into an online compiler, re-running after every edit, squinting at wrong answer output trying to spot the difference. It's frictions, this is for you.↵
↵
**at adds up, especially under time pressure.↵
↵
So I built kJudge** is, a CLI tool I built for local testing of CodeforcesF solutions. Everything runs in your terminal.↵
↵
**Repo**: https://github.com/Byte-ne/kJudge ↵
**Docs**: https://byte-ne.github.io/kJudgeThe core idea: fetch samples automatically, watch your file for changes, and show you a clean diff when your output doesn't match. No browser tab switching, no manual input pasting.↵
↵
## What it does:↵
↵
- **Auto-fetches samples** from Codeforces—> no manual copy-pastingfor any problem — just point it at the problem URL↵
- **Watch mode** —> re-runs your solution on every file save, tightso the feedback loop is as tight as possible↵
- **WA diffs** —> shows expected vs actual output shown side by side, not just "wrong answer on test 2"↵
- **Contest scaffolding** —> one command sets up folders and templates for allevery problems in one command↵
- **Any IDE, any OS** —> pure CLI, supports C++, Python, and Java (hoping to add more in the near future)↵
↵
# Preview↵
↵
Here is how the CLI watch mode looks, with a simple string & implementation problem called [Petya and Strings](https://mirror.codeforces.com/problemset/problem/112/A)a round↵
- Works with C++, Python, and Java; pure CLI so it's IDE and OS agnostic↵
↵
Setup is a single binary download from Releases — run it once and it adds itself to PATH. Full guide in the docs.↵
↵
↵
↵
## Setup↵
↵
Download the binary from [Releases](https://github.com/Byte-ne/kJudge/releases), run it once & it adds itself to your PATH. Full guide in the [docs](fd/a0fdda98daf0f062f817f33b654a6c86703b677f.png)↵
↵
Repo: https://github.com/Byte-ne/kJudge↵
Docs: https://byte-ne.github.io/kJudge).↵
↵
---↵
↵
This is my first public tool, — built because I wanted it for my own practice. Feedback, issues, and feature requests are all welcome .. what would you want added? sessions and figured it might be useful for others in the same boat. If something's broken or you want a feature, open an issue or drop a comment.↵
↵
If you've ever wasted contest time copy-pasting samples into an online compiler or fighting with IDE extens
↵
During contests, I kept losing time on things that had nothing to do with solving the problem — manually copying samples into an online compiler, re-running after every edit, squinting at wrong answer output trying to spot the difference. It's friction
↵
**
↵
So I built kJudge
↵
**Repo**: https://github.com/Byte-ne/kJudge ↵
**Docs**: https://byte-ne.github.io/kJudge
↵
↵
- **Auto-fetches samples** from Codeforces
- **Watch mode** —
- **WA diffs** —
- **Contest scaffolding** —
- **Any IDE, any OS** —> pure CLI, supports C++, Python, and Java (hoping to add more in the near future)↵
↵
# Preview↵
↵
Here is how the CLI watch mode looks, with a simple string & implementation problem called [Petya and Strings](https://mirror.codeforces.com/problemset/problem/112/A)
- Works with C++, Python, and Java; pure CLI so it's IDE and OS agnostic↵
↵
Setup is a single binary download from Releases — run it once and it adds itself to PATH. Full guide in the docs.↵
↵
, run it once & it adds itself to your PATH. Full guide in the [docs](
↵
Repo: https://github.com/Byte-ne/kJudge↵
Docs: https://byte-ne.github.io/kJudge
↵
---
↵
This is my first public tool
