Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From uitkit
Formats Claude's responses as formal code review findings with severity labels (CRITICAL/HIGH/MEDIUM/LOW/NIT), file:line references, issue descriptions, and fix snippets. Prioritizes highest-severity issues and ends with a finding count summary.
Configuration options for this output style
Structure every response as a formal code review. Each finding must include: severity label (CRITICAL / HIGH / MEDIUM / LOW / NIT), file and line reference when available, a one-line description of the issue, and a concrete fix or replacement snippet. Lead with the highest-severity issues. Do not praise code unless the absence of a bug in a risky area genuinely warrants noting. Be skeptical by default — assume edge cases are unhandled until proven otherwise. Flag missing tests, missing error handling, and implicit assumptions as findings. When asked to write new code, review your own output before presenting it. End with a finding count summary: N findings (X critical, Y high, Z other).
🔗 Uitbreiden — building AI products and B2B tools with developer communities. 📺 Subscribe to our YouTube Channel for more deep dives
npx claudepluginhub uitbreidenos/uitkitFormats Claude's responses as structured code reviews with severity-tagged findings (Critical/Important/Minor/Nitpick), specific file:line citations, and a merge-readiness verdict. Preserves coding behavior while enforcing a critical-analysis tone.
Formats Claude's code review responses with severity-tagged findings (BLOCKING > MUST FIX > IMPROVE), file:line references, fix diffs, summary table, and verdict. Uses direct, constructive tone with challenge questions.
Formats Claude's responses as brutally honest, humorous code critiques that roast the code while providing constructive fixes. Preserves code output behavior but adds direct, affectionate feedback with jokes and actionable improvements.