scorched-earth
SolidObsessively 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'.
Install
Quality Score: 82/100
Skill Content
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
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.
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.
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.