Diagnose which rules loaded, which didn't, and why. Reads the InstructionsLoaded audit log and compares against expected rules.
Remove stale agent worktree directories and their orphaned branches. Run after parallel agent work or when .claude/worktrees/ accumulates cruft.
Starts a structured interview to diagnose WordPress issues, then proposes a ranked list of solutions.
Generate a user-facing test checklist from git diff, or execute an existing test plan via Playwright.
Review auto-memory for the current project. Shows accumulated learnings, identifies noise, and helps promote permanent patterns to CLAUDE.md, rules, or skills.
Discover all files for a block or component, trace the editorial and front-end user journeys, and write a journey document to docs/journeys/.
Open an app in Playwright and explore it as a real user with no prior knowledge. Report UX findings per page, test core flows, and suggest improvements.
Use when the user asks to audit, review, investigate, check, scan, "look at", or "find issues in" code — anything that sounds like a diagnostic request without an explicit fix…
Use when reviewing Swift 5.5+ code containing `await`, `actor`, `Task { }`, `@MainActor`, `@unchecked Sendable`, cancellable timer/deadline handles, or long-lived `for await`…
Recovery protocol for tool failures and search budgets. Use when Edit fails repeatedly on the same target, when hooks may have modified file contents between operations, or when…