JHostalek

Use after making changes to run the project's quality gates and report pass or fail for each relevant check.

Use when running the full audit sweep on a scope — runs the focused audit dimensions (necessity, structure, patterns, correctness, error handling, logs, perf, security, tests, complexity, comments) as a parallel-worktree workflow that integrates in dependency order. Triggers on "audit", "full audit", "audit everything".

Use when the user asks to create or update a pull request for the current branch.

Use when the user wants to improve website search visibility, AI search visibility, schema markup, indexing, metadata, or keyword targeting.

Use when the user asks to merge another branch into the current branch, pull upstream changes without rebasing, or resolve merge conflicts.

Use when auditing and fixing performance hot paths in a scope — N+1 queries, overfetching, wasted recomputation, blocking hot paths, unbounded growth. Triggers on "audit performance", "fix slow paths", "check for N+1", "performance review".

Use when auditing and fixing security in a scope — injection (SQL, shell, template), auth/authz gaps, secrets in code or logs, weak crypto, missing validation at trust boundaries, XSS, SSRF, path traversal. Triggers on "audit security", "security review", "fix vulnerabilities", "OWASP check".

Use when a task is multi-step, ambiguous, or high-impact and you need an executable implementation plan before editing code.

Use when the user asks how to do something, wants a skill for a task, or wants to discover and install new agent capabilities.

Use when rewriting an existing skill so Opus 4.8 (or any frontier reasoning model) executes it with better judgment, less scaffolding, and tighter calibration. Do NOT trigger for new skills from scratch (use skill-creator) or for prompt artifacts (use prompt).

Use when a task spans multiple files or workstreams and benefits from parallel implementation by an agent team.

Use when the user needs design exploration, multiple distinct solution directions, or tradeoff-driven options before implementation.