y_soul090's blog

By y_soul090, history, 3 hours ago, In English

Hi everyone!

I've been solving CSES problems for a while, and one thing kept bothering me:

I was constantly switching between CSES → editor → terminal → browser for almost every problem.

So I built cses-kit.

The goal is simple: keep the CSES workflow inside your terminal.

The workflow

Fetch → Code → Test → Submit

For example:

cses new missing-number
cses run missing-number
cses submit missing-number

Instead of manually creating files, copying samples, compiling, and repeatedly jumping back to the browser, the CLI handles the repetitive parts so you can focus on solving the problem.

What it can do today

  • Fetch CSES problems locally
  • Create starter solution files
  • Run sample test cases
  • Submit solutions directly to CSES
  • C++ and Python support
  • VS Code / Cursor integration
  • Local execution with sanitizers

Everything is open source and designed to stay small and hackable rather than becoming a heavy IDE.

What I'm working on next

I'm currently working on:

  • Built-in stress testing
  • More programming languages
  • Better local testing
  • Improved error handling and developer experience

The stress-testing workflow I'm aiming for is:

Generator → Random Test Input → Brute / Reference Solution → Optimized Solution → Compare Outputs → Counterexample

The idea is to make finding hidden edge cases much easier without writing custom bash scripts every time.

I'd love feedback

I'm especially interested in hearing from people who solve CSES regularly.

A few things I'd love your thoughts on:

  • What parts of your CSES workflow feel repetitive today?
  • What would make a CLI genuinely useful for you?
  • Which language should I prioritize next?
  • Would built-in stress testing be something you'd actually use?

I'm also trying to make this a community-driven project, so feature requests, bug reports, and pull requests are very welcome.

GitHub: https://github.com/yatharthsol090/cses-kit

If you solve CSES regularly, I'd love to hear what you'd want from a tool like this. Feedback, feature ideas, issues, and PRs are all welcome!

  • Vote: I like it
  • -1
  • Vote: I do not like it

»
3 hours ago, hide # |
 
Vote: I like it +1 Vote: I do not like it

not bad, good luck to your current works!

  • »
    »
    3 hours ago, hide # ^ |
     
    Vote: I like it 0 Vote: I do not like it

    Thanks! Really appreciate it. If you end up trying it out, I'd love to hear any feedback or things you'd like to see added.