roast-gen_skill

Overview

This skill gives your code a humorous but practical roast and produces actionable fixes. It inspects files or whole projects with one command and returns a candid review that highlights code smells, anti-patterns, and questionable decisions. Use it to get fast, honest feedback without bothering a teammate.

How this skill works

The tool parses your codebase and runs static analysis heuristics to find naming issues, complexity hotspots, duplication, and bad patterns. It formats feedback as a roast — witty commentary paired with concrete suggestions and code-level fixes. You can target single files, directories, and choose roast intensity levels from mild to brutal.

When to use it

• You want a quick, standalone code review without involving others
• During retros or team sessions to surface tech debt in a lighter tone
• Onboarding new developers to show common pitfalls and better alternatives
• Before a PR to get an independent sanity check
• When assessing legacy code you don’t fully understand

Best practices

• Start with a mild roast to get familiar with the feedback tone
• Run roasts on focused areas (functions, modules) to avoid overwhelming suggestions
• Treat jokes as signals — prioritize the listed fixes over the humor
• Integrate into pre-merge checks for recurring patterns you want to eliminate
• Share roast results with the team and track fixes as tasks

Example use cases

• Roast a single file: quickly expose naming and small logic issues
• Roast an entire src folder to map out large-scale refactor needs
• Use gentle mode for learning sessions with juniors
• Use brutal mode to challenge senior engineers and reveal hidden debt
• Run before major releases to catch risky anti-patterns