scorched-earth

Solid

Obsessively thorough analysis. Three modes: build (find every issue in a codebase), intake (extract everything from a URL or reference), research (exhaustive investigation of a topic). Use when surface-level isn't enough and you need certainty nothing was missed. Triggers: '/scorched-earth', 'go scorched earth', 'find everything', 'leave no stone unturned', 'I need to be thorough'.

AI & Automation 3 stars 0 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
20
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Scorched Earth Unrelentingly, obsessively thorough analysis. This skill exists for one reason: to make absolutely certain nothing is missed. Not "pretty thorough." Not "good enough." Every file, every function, every claim, every detail — examined, verified, logged. This is the skill you reach for when the cost of missing something is higher than the cost of being slow. It will take too long. It will find things you didn't ask about. It will be almost annoying in its thoroughness. That's the point. --- ## The Rules These rules override every default behavior. They exist because LLMs are trained to be convenient, fast, and concise. This skill is none of those things. ### What you MUST do 1. **Enumerate before you examine.** List everything first — every file, every section, every source. Create a task for each. Then examine them one by one. Never start analyzing until you know the full surface area. 2. **Track your progress.** Use tasks. Every area to examine gets a task. Mark it in-progress when you start, completed when you finish. If the task list is empty and you haven't examined everything, something is wrong. 3. **Write findings to disk incrementally.** Never hold findings only in context. After examining each zone or source, append findings to the report file on disk immediately. Context can compact at any time — what's on disk survives. 4. **Be specific or be silent.** Every finding must name the exact file, the exact line, the exact function, the exact pro...

Details

Author
catcatcatstudio
Repository
catcatcatstudio/cat-skills
Created
5 months ago
Last Updated
6 days ago
Language
TypeScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Solid

skill-name-here

What this reviews or produces, then when to reach for it. Use when user says '<a phrase they would actually type>', '<another one>', or when working in <the files this applies to>. This is the only text the model reads when deciding whether to load the skill, so write triggers, not a summary.

8 Updated 2 weeks ago
anmolnagpal
Code & Development Listed

scour

The reality-check hotline. Mid-conversation, leave the closed room and go to the internet to ground what was just said against how the world actually does it. Two faces - verify (we concluded something confidently; pull the load-bearing claims and check each against real fetched sources - confirmed / wrong / oversimplified / outdated / no-consensus) and discover (we're stuck or starting fresh; find the dominant pattern and the gotchas). Use when the user says "scour this", "are we on the right page?", "is this actually how people do it?", "go check the internet", "make sure we're not confidently wrong", or asks how something is normally done. Fast and conversational like isomorph - never writes files, never answers from memory.

0 Updated 3 weeks ago
kennykankush
Code & Development Listed

getff

Use when treating any codebase rule (architectural, naming, dependency, test-quality, contract, SLO) as an executable test that fails the build when violated, or when the user asks about enforcing code quality, fighting AI-generated code drift, setting up linters/tests/CI/pre-commit hooks, designing review processes, mutation testing, contract testing, fitness functions, observability-driven development, SLO-as-code, or any version of "how do I make my codebase resistant to AI agents breaking my conventions". Also trigger on any mention of ArchUnit, Stryker, Pact, dependency-cruiser, AI Factory (aif), Husky, lint-staged, ESLint flat config, Zod validation strategy, or shift-left/shift-right testing. Strongly trigger when the user mentions Claude Code, Cursor, or Copilot writing code that "looks fine but is wrong" — that is the core problem this skill addresses.

0 Updated today
artyhoo