Use this skill ANY time you need to search for code structure, refactor symbols, analyze impact, find dead code, or trace dependencies. ALWAYS invoke BEFORE using grep for structural code analysis. Trigger categories: structural pattern search (e.g. useEffect without deps, async without try-catch, fetch calls outside…
AST-based structural code search, lint, and rewrite via the ast-grep (sg) CLI. Use when a search or edit is about code SYNTAX STRUCTURE rather than text: finding every call site of a function, matching shapes such as "async functions without try/catch" or "useEffect without a dependency array", codemods that rewrite…
Execute this meta-skill ALWAYS at the end of complex tasks, debugging sessions, or when learning a new project codebase quirk. You MUST trigger this skill to codify hard-won lessons into reusable project rules (saving them to project-specific AI instruction files or a new SKILL.md). Do NOT close a complex task without…
Use this skill for any structural code search or replacement task — it is the right choice whenever grep/sed would feel clunky or risky. Trigger on ANY of these patterns: Structural find-and-replace across a codebase: "replace all fetch(url, options) calls with the new fetchWithRetry signature", "rename the first…
Trigger this AUTOMATICALLY anytime you encounter a stack trace, test failure, production bug, or unexpected behavior. Do NOT guess the fix or propose code changes before explicitly triggering this skill. This skill mandates a strict data-gathering and hypothesis phase before you are permitted to edit ANY source code.
★not rated 4 26d agoA64 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: