PROACTIVELY load this skill when the user asks to "debug this", "review my code", "refactor this file", or "security audit". Unified engineering capabilities for debugging, code review, refactoring, and testing.
Unified engineering capabilities for debugging, code review, refactoring, and security audits. Automatically routes to the appropriate workflow when you request debugging, reviews, refactoring, or security analysis.
/plugin marketplace add Git-Fg/thecattoolkit/plugin install git-fg-thecattoolkit@Git-Fg/thecattoolkitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/architecture-checklist.mdreferences/debugging-protocol.mdreferences/refactoring-patterns.mdreferences/review-checklist.mdreferences/security-checklist.mdreferences/tdd-protocol.mdworkflows/architecture.mdworkflows/code-review.mdworkflows/debug.mdworkflows/prototype.mdworkflows/refactor.mdworkflows/security-audit.mdworkflows/test-driven-development.mdworkflows/testing.md<foundational_knowledge>
BEFORE executing ANY workflow in this skill that involves MODIFYING code, you MUST read:
references/security-checklist.md - OWASP Top 10, security vulnerabilities, and safety protocolsFor READ-ONLY workflows (review, analyze), security checklist is recommended but not mandatory.
WHY: Engineering workflows that modify code can introduce security vulnerabilities, data corruption, or system instability. The security checklist contains non-negotiable safety protocols.
EXECUTION RULE: Read foundational knowledge IMMEDIATELY upon workflow invocation. For modification workflows, this is non-negotiable. </foundational_knowledge>
<routing> ## Intent-Based RoutingAnalyze the task description to determine the appropriate workflow:
| Intent Detected | Route To Workflow | Foundational Context |
|---|---|---|
| "debug", "fix error", "crash", "issue" | workflows/debug.md | Security checklist (if modifying) |
| "review", "audit code", "quality check" | workflows/code-review.md | Review checklist |
| "refactor", "clean up", "modernize" | workflows/refactor.md | Security checklist + Refactoring patterns |
| "security audit", "vulnerability", "pen test" | workflows/security-audit.md | Security checklist (mandatory) |
| "tdd", "test-driven", "test-first", "red-green-refactor" | workflows/test-driven-development.md | TDD protocol (mandatory) |
| "test", "coverage", "testing" | workflows/testing.md | No additional context needed |
| "architecture", "system design", "design pattern" | workflows/architecture.md | Architecture checklist |
| "prototype", "spike", "explore", "draft", "vibe code" | workflows/prototype.md | None (draft phase), then full rigor |
Route immediately to the matching workflow without asking questions. </routing>
workflows/debug.md - The 6-Phase Debug Protocolreferences/debugging-protocol.md - Detailed debugging methodologiesworkflows/code-review.md - PR Review Workflowreferences/review-checklist.md - Correctness, Security, Performance checklistworkflows/refactor.md - Refactoring Workflowreferences/refactoring-patterns.md - Code smells and SOLID principlesworkflows/security-audit.md - Security Assessment Workflowreferences/security-checklist.md - OWASP Top 10 focus areasworkflows/test-driven-development.md - Red-Green-Refactor Workflowreferences/tdd-protocol.md - The Iron Law and methodologyworkflows/testing.md - Testing Implementation Workflowworkflows/architecture.md - System Design & Architecture Analysisreferences/architecture-checklist.md - Architecture quality criteriaworkflows/prototype.md - Draft-then-Harden WorkflowThis skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.