Individual skill

octocode-roast

Use when code needs a blunt evidence-backed roast or memorable critique: smell inventory, debt ranking, hot-path autopsy, savage/diff review, security or performance sins, or practical redemption paths. Phrases like roast this, brutal review, top sins, cleanup debt. Polite evidence-first PR review → octocode-research.

skills/octocode-roast/SKILL.md

Read pinned source

Source commit c265e3f9413161c900cbf4aa70d451b8e6b3920a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 957
Repository last updated: Nov 6, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

ai Repository topic
claude-ai Repository topic
cursor-ai Repository topic
development Repository topic
mcp Repository topic
modelcontextprotocol Repository topic
octocode Repository topic
ai-agents Repository topic
ai-tools Repository topic
code-intelligence Repository topic
security Derived category
research Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 2,535 bytes
SKILL.mdcore · 4,026 bytes
references/improve-loop.mddoc · 679 bytes
references/language-sins.mddoc · 1,994 bytes
references/octocode.mddoc · 873 bytes
references/parallel-roasting.mddoc · 2,631 bytes
references/redemption-flow.mddoc · 1,687 bytes
references/roast-playbook.mddoc · 2,242 bytes
references/sin-catalog.mddoc · 2,210 bytes

Read excerpt


# Octocode Roast

Sharp code critique with proof and a repair path.
Flow: `TARGET → INSPECT → INVENTORY → AUTOPSY → CHECKPOINT → REDEEM`.

## Lobby rules
- Target patterns, never people; obey the requested scope and widen only with approval.
- Cite or drop it: every major finding needs an exact anchor, impact, confidence, and repair move.
- Obey explicit user targets first. Only widen to staged/diff/repo scope when no target was given or the user asks for a broader pass.
- Punch the code, not the coder; avoid insults about ability, identity, or experience.
- Never reveal a secret; redact values and use restrained language for security or production-sensitive findings.
- Rank confirmed security, data loss, correctness, and user-impacting performance above style or taste.
- Default to medium tone; use savage/nuclear only when explicitly requested. Do not edit or install before consent.
- Stop when: the target resolves to no files; the checkpoint is reached — important versus redundant findings summarized, nothing edited yet; a repair, a scope widening, or an install needs consent; savage/nuclear tone was not requested; or evidence is pattern-only — report the lead with its confidence instead of asserting exploitability, latency, or outage.