agentleFS
LucfaceLucface/claude-skills/skills/grill/SKILL.md

grill

Skill1 starsChanged 3 days agoMITView on GitHub

Adversarial code review — challenge your code harshly, find what will break in production. Inspired by Boris Cherny's setup.

  • Reads credentials

92 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use write-skill, root-cause and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NoaiRoxSkill

    write-skill

    Use when creating a new skill, editing an existing skill, or verifying a skill works before deployment.

    Also in 5 projects that use this

  • Ingramradical235Skill

    root-cause

    Structured root cause analysis using WHERE (MECE decomposition) then WHY (causal structure diagrams) pipeline. Includes coin-flip detection, logical-leap detection, and vicious cycle intervention. Use when buffer enters YELLOW/RED, when metrics stall, or when Actions execute but don't produce results.

    Also in 4 projects that use this

  • Neko-Catpital-LabsSkill

    prove-it

    Shared evidence rule for investigating, diagnosing, debugging, proving, or explaining what happened or why for any problem or situation: do not assert something is fixed, working, passing, merged, or running unless you personally observed it this turn and can show what you saw; do not assert it was caused by X until a repro and controlled isolation prove that cause.

    Also in 4 projects that use this

  • sahinSkill

    execute

    Also in 5 projects that use this

  • assisjpSkill

    file-pr

    Prepare and open or update an authorized pull request with a concise problem-first description and verifiable evidence. Use when the user asks to create, file, open, or update a PR. Do not use merely to review a diff or when publication is not authorized.

    Also in 3 projects that use this

  • Arman-KudaibergenovSkill

    write-plan

    Этот скилл MUST быть вызван когда есть design.md и нужно разбить доработку на атомарные задачи (2-5 мин) с точными путями файлов и критериями проверки в tasks.md. SHOULD также вызывать как промежуточный шаг между brainstorm и subagent-dev. Do NOT использовать для обсуждения идеи — используй brainstorm; для выполнения задач — используй subagent-dev.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 71 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No args → Full 3-agent review of changed files

    line 18
  2. Distinctive:

    If no files found: ask what to review and stop.

    line 32
  3. Very specific:

    If tests fail after fixes, revert the failing fix (git checkout -- <file>) and note in report.

    line 150

“Common” is measured: kept by at least 6 in 10 of the 71 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Grill (/grill)

Adversarial code review that actively tries to break your code.

Time budget: 10 min total (agents ~5 min, synthesis + fixes ~5 min). Abort at 10 min with partial report.

Arguments

Parse $ARGUMENTS string:

  • --security → Security-only mode (just Agent 2)
  • --perf → Add performance stress-test agent (Agent 4)
  • --files "a.ts,b.ts" → Target specific files instead of git diff
  • --report-only → No auto-fixes, just report
  • No args → Full 3-agent review of changed files

Instructions

Step 1: Identify Target

git diff --name-only HEAD~1   # committed changes
git diff --name-only          # unstaged changes
git diff --name-only --cached # staged changes

Merge all three lists, deduplicate. If --files was passed, use those instead.

If no files found: ask what to review and stop.

Filter out non-code files (images, lockfiles, .env). If >20 files, ask user to narrow scope.

Step 2: Dispatch Adversarial Reviewers

Launch agents in parallel (Task tool, subagent_type: "general-purpose", model: "sonnet"). Each agent prompt MUST include: "Read each file using the Read tool before analyzing."

Agent 1 — The Breaker:

You are a hostile QA engineer. Your job is to BREAK this code. Read each file listed below using the Read tool, then find:
- Edge cases that will crash in production
- Race conditions and concurrency issues
- Input combinations that cause unexpected behavior
- State transitions that lead to corruption
- Error paths that swallow failures silently

Files to read and review: [list with full paths]

Be specific. Show the exact input/scenario that breaks it.
Do NOT suggest improvements — only find what's broken.
Rate each: Critical / High / Medium / Low.
If nothing is broken, say "No issues found" — don't invent problems.

Agent 2 — The Security Auditor:

You are a penetration tester reviewing this code. Read each file listed below using the Read tool, then find:
- Injection vulnerabilities (SQL, XSS, command)
- Authentication/authorization bypasses
- Data exposure through error messages or logs
- Missing input validation at trust boundaries
- Secrets or credentials in code
- OWASP Top 10 violations

Files to read and review: [list with full paths]

Rate each finding: Critical / High / Medium / Low.
Show the attack vector for each.
If the code has no security surface (e.g. pure utility), say "No security issues found."

Agent 3 — The Skeptic:

You are a senior engineer who thinks this code is wrong. Read each file listed below using the Read tool, then challenge:
- Does this actually solve the stated problem?
- Are the types correct or just making the compiler happy?
- Will this scale to 10x/100x current load?
- Are error messages helpful or misleading?
- Is the abstraction level right or over/under-engineered?

Files to read and review: [list with full paths]

For each concern, explain the concrete consequence of not fixing it.
Rate each: Critical / High / Medium / Low.
If the code is solid, say so — don't manufacture concerns.

Agent 4 — The Stress Tester (only if --perf flag):

You are a performance engineer. Read each file listed below using the Read tool, then find:
- O(n^2) or worse algorithms on unbounded input
- Missing pagination/limits on queries
- N+1 query patterns
- Unbounded memory growth (accumulating arrays, missing cleanup)
- Blocking operations in async paths

Files to read and review: [list with full paths]

Rate each: Critical / High / Medium / Low.

Skip Agent 1 and 3 if --security flag is set.

Step 3: Synthesize Findings

Deduplicate across agents. Merge into severity-sorted report:

## Grill Report — [date]
Files reviewed: [list]
Agents: [which ran]

### Critical (fix before shipping)
- [finding] — [file:line] — [agent]

### High (fix soon)
- [finding] — [file:line] — [agent]

### Medium (track for later)
- [finding] — [file:line] — [agent]

### Low (nice to fix)
- [finding] — [file:line] — [agent]

### Clean
- [things that passed all reviews]

### Verdict: SHIP / HOLD / BLOCK

Verdict rules: any Critical → BLOCK. 3+ High → HOLD. Otherwise → SHIP.

Step 4: Fix (unless --report-only)

  • Critical items: Present each fix to user for confirmation before applying. Never auto-fix security code silently.
  • High items: List with recommended fixes, let user choose which to apply.
  • Medium/Low: Note in report only.

Step 5: Re-verify

Detect project type and run tests:

  • package.json with bun.lockb → bun test
  • package.json without bun.lockb → npm test
  • pytest.ini / pyproject.toml / tests/ with .py → pytest
  • Gemfile → bundle exec rspec
  • Makefile with test target → make test

If tests fail after fixes, revert the failing fix (git checkout -- <file>) and note in report.

Source

Inspired by Boris Cherny's Claude Code tips (https://x.com/bcherny/status/2017742741636321619), the item "Challenge Claude: Grill me on these changes".

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.