roast

Review codebases and pull requests for security risks and correctness flaws.

6|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/GeekKingCloud/skills --skill roast-geekkingcloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roast
Source: https://github.com/GeekKingCloud/skills/tree/main/roast
Command: npx skills add https://github.com/GeekKingCloud/skills --skill roast-geekkingcloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates superficial, inconsistent code reviews that miss critical security risks, correctness flaws, and maintainability debt, delivering structured, evidence-backed feedback instead of vague opinions.

Core Features & Use Cases

  • Security-First Review: Prioritizes critical security flaws like injection, auth bypasses, and secret exposure over minor style issues.
  • Structured Grading: Assigns an A-F grade based on overall codebase health, with clear severity ratings for all findings.
  • Use Case: Use it to audit a new PR before merge, review a legacy codebase for hidden risks, or validate generated code for production readiness.

Quick Start

Use the roast skill to review the code in the current workspace and deliver a full security-focused audit report with findings and a grade.

Frequently Asked Questions about roast

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a security audit on a pull request before merging?

A security audit on a pull request identifies critical risks like injection and auth bypasses, delivering severity-rated findings and fix directions before merge. This process prioritizes security flaws over minor style issues to ensure release readiness.

What is the best way to grade codebase health and engineering standards?

Grading codebase health involves assessing correctness flaws, maintainability debt, and security risks to assign an overall A-F grade. This structured grading aligns with engineering best practices to provide evidence-backed feedback.

How does a security-first code review handle generated code validation?

Security-first code review for generated code validation targets hidden critical risks and correctness flaws to determine production readiness. It applies strict risk assessments and delivers evidence-backed findings with clear impact and fix directions.

Can I assess legacy codebase risks without manual line-by-line inspection?

Assessing legacy codebase risks can be automated by performing directed target reviews that identify critical risks, correctness flaws, and maintainability debt. This delivers severity-rated findings and an overall grade without manual inspection.

Does a strict code review check for secret exposure and auth bypasses?

A strict code review does check for secret exposure and auth bypasses, prioritizing these critical security vulnerabilities over minor style issues. It provides structured, evidence-backed feedback to eliminate superficial security misses.