agentleFS
renatorozasrenatorozas/claude-code-config/.claude/skills/grill/SKILL.md

grill

Skill1 starsChanged 8 months agoMITView on GitHub

Adversarial code review. Don't let me ship until the changes pass your scrutiny.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 64 edited versions we read keep these.

  • 3

    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. Very specific:

    Run git diff <base>...HEAD to see all changes on this branch

    line 14
  2. Distinctive:

    If NEEDS WORK or BLOCK: list each issue with file, line, and what to fix

    line 22
  3. Distinctive:

    After I make fixes, re-review from step 1

    line 23
  4. Distinctive:

    Only give SHIP IT when every issue is resolved

    line 24

“Common” is measured: kept by at least 6 in 10 of the 64 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

Adversarial code review. Don't let me ship until the changes pass your scrutiny.

Steps:

  1. Determine the base branch (main or master)
  2. Run git diff <base>...HEAD to see all changes on this branch
  3. Review every change as a skeptical staff engineer:
    • Logic errors, edge cases, race conditions
    • Missing tests for new or changed behavior
    • Breaking changes to public APIs
    • Security concerns (injection, auth, data exposure)
    • Performance regressions
  4. Rate the changes: SHIP IT / NEEDS WORK / BLOCK
  5. If NEEDS WORK or BLOCK: list each issue with file, line, and what to fix
  6. After I make fixes, re-review from step 1
  7. Only give SHIP IT when every issue is resolved

Download now (ZIP)

  • Other versions78 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 78

    1. kirodotdev/KiroCrew★ 4.7ksame name
    2. crbnos/carbon★ 2.8ksame name
    3. JuliusBrussee/cavekit★ 1.1ksame name
    4. SethGammon/Citadel★ 927same name
    5. nagi-studio/skills★ 301same name
    6. KerberosClaw/kc_ai_skills★ 79same name
    7. alamops/skills★ 53same name
    8. Kanevry/session-orchestrator★ 53same name
    9. oakreader/oakreader★ 46same name
    10. manusco/resonance★ 38same name

    68 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use write-skill, prove-it 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 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

    • 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 3 projects that use this

    • 0x43e96fSkill

      kickoff

      "Interview Me" 启动协议。需求不清晰时,在开始实施之前先反问用户,收集足够上下文再规划。 触发词: /kickoff、"先问我问题再开始"、"在动手之前了解需求"、"需求还不清楚"

      Also in 4 projects that use this

    • sahinSkill

      execute

      Also in 4 projects that use this

    • AnthropicSkill

      debug

      Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

      Also in 12 projects that use this

  • In this repository8 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.