Use when the user says "check docs", "audit docs", "doc quality", "doc slop", "stale docs", or wants to verify documentation accuracy and tone against the actual codebase.
Use when the user says "find tech debt", "audit code quality", "what needs cleanup", "show me debt", "code health check", "scan for smells", or wants a comprehensive quality assessment before planning a refactor or sprint.
Structured brainstorming and design gate for deep problem understanding before implementation. Use this skill whenever the user says "brainstorm", "think through", "explore this problem", "let's think about", "what are the angles", "help me understand", "design this", or wants to deeply analyze a problem, feature, architecture decision, or technical challenge before writing code. Also trigger when the user is about to jump into implementation of something non-trivial and hasn't explored the problem space yet — a gentle nudge toward brainstorming prevents wasted effort from unexamined assumptions. This skill is about understanding the problem deeply and producing an approved architectural design, not writing code.
High-quality code patterns with strict types, functional programming, and immutability. Use when writing ANY code in any language. Trigger whenever the user writes, reviews, or refactors code — even if they don't explicitly ask for "quality" or "strict" patterns. This skill applies to TypeScript, Python, and any future languages. Always load this skill for implementation tasks.
Deep code review that hunts for subtle bugs and, when a plan/design document is provided, verifies the change actually accomplishes what the plan describes. Invoke explicitly with /code-review — this skill never triggers automatically. Use when the user says "/code-review", "review my code", "review this change", or "review against the plan".
Inviolable rules injected into every sub-agent context as a preamble. Not directly invocable — loaded by the orchestrate skill and prepended to all sub-agent prompts to enforce scope discipline, verification rigor, and safe coding practices.
Enforce minimum test coverage threshold for tarash-gateway. Use this skill after writing or modifying code to check that unit test coverage meets the required minimum. If coverage is below threshold, generates a test gap spec and invokes the orchestrate skill to implement missing tests automatically.
Analyzes dirty working trees, groups related changes into logical commits using hunk-level staging, and writes conventional commit messages with proper prefixes (feat, fix, refactor, etc.). Triggers when committing code, staging changes, splitting changes into commits, or organizing git changes. Use whenever the user says 'commit', 'commit this', 'commit my changes', 'create commits', 'split into commits', 'stage and commit', or asks for help with their git changes. Does not handle branch management, rebasing, merging, or pushing.