stresst

🔥Insurance against vibe coding

Are you a Vibe Coder or a Jive Coder?

AI can write code, but can you debug it? stresst introduces realistic bugs into real codebases to test if developers truly understand what they're shipping.

What is stresst?

🤖 AI-Powered Bug Generation

Uses Claude AI to introduce subtle, realistic bugs that developers actually make — off-by-one errors, null pointer issues, async/await mistakes, logic inversions, and more.

📊 Configurable Difficulty

Choose your stress level: Low (1-2 bugs), Medium (2-3 bugs), or High (3-5 devious bugs). Optionally focus on specific areas like async/await or null handling.

🔔 Realistic Bug Reports

Receive user-friendly symptom descriptions like "The posts are showing up blank" or "The app crashes when I select an item" — just like real production issues.

📋 Share & Collaborate

Copy bug reports to share with colleagues via email or Slack. Perfect for team training sessions, code reviews, or interview scenarios.

Receive realistic bug reports describing symptoms — not solutions
Screenshot showing bug report notifications with realistic user complaints

Why I Built This

AI code generation is everywhere — Cursor, Copilot, ChatGPT. Developers are shipping code faster than ever. But here's the uncomfortable question: do they actually understand what they're shipping?

When AI-generated code breaks (and it will), can your team debug it? Or are they just prompting until the errors go away?

stresst provides a challenging and engaging way for developers to learn how to fix bugs and diagnose code. It's essential for anyone using code-gen tools — because when things go wrong, it's imperative to be able to get things back on track.

How It Works

1

Connect

Sign in with GitHub to access your repositories

2

Select

Choose a repo, branch, and commit to stress

3

Stress

AI introduces realistic bugs — share & debug!

Select a commit and configure stress level
Screenshot showing the commit selection interface with stress level configuration

The Stress Process

When you hit "Stress", our AI analyzes your codebase, identifies the most interesting files to inject bugs into, and creates a new branch with realistic, hard-to-spot issues. You'll get a bug report describing symptoms — just like a real user complaint — without revealing where the bugs are.

Behind the scenes
Creating branch~5-30s
Analyzing files~5-30s
Stressing out your code~1-2 min
Committing changes~5-30s
Finalizing~5-30s
Total time: ~2-4 minutes

Scoring System

Once you've fixed the bugs and committed your changes, return to stresst to check your score. The system automatically detects your start and completion commits and grades you based on how quickly you fixed all the bugs.

🌟
A Grade
Outstanding
🔥
B Grade
Great Job
👍
C Grade
Good Work
💪
D Grade
Keep Practicing
DifficultyABCD
🌱 Easy0-5 min5-10 min10-15 min15+ min
🔥 Medium0-7 min7-11 min11-15 min15+ min
💀 Hard0-10 min10-15 min15-20 min20+ min
Check your score after fixing the bugs
Screenshot showing the scorecard with grade and time taken

Choose Your Codebase

Your Own Codebase

Use any repository you have access to. Great for testing your team's familiarity with your actual production code.

Requires write access to create branches
Recommended

Our Practice Codebases

Fork one of our public "dummy" repositories designed specifically for practice. No risk to your real code, and they're structured to be great learning material.

One-click fork available after sign in

Available Practice Repositories

Getting Started

Prerequisites

  • Node.js 18+
  • A GitHub account
  • An LLM provider — Anthropic (recommended), OpenAI, or a local LLMAnthropic is most robustly tested. Local requires a capable machine.

Quick Setup

$ git clone https://github.com/brenoneill/stresst.git
$ cd stresst && npm install
$ npm run dev

See the README for full environment setup including GitHub OAuth and Anthropic API configuration.

Ready to stress test your skills?

Connect your GitHub account and start building real debugging muscle today.