rune

Rune skill ecosystem — interconnected workflows for the full project lifecycle. Use /rune <action> to invoke skills.

Lie detector for agent claims — validates every completion claim has actual evidence. Default-FAIL mindset. Use as final gate before merge/commit.

Performance regression gate — detects N+1 queries, sync-in-async, missing indexes, memory leaks, bundle bloat. Investigate only, does NOT fix. Use before commit or deploy.

Create structured implementation plans. Produces master plan + phase files for non-trivial work (3+ phases, 5+ files). Use before multi-phase implementation.

Pre-commit quality gate — catches 'almost right' code. Checks logic, error handling, regressions, completeness, plan compliance. BLOCK verdict stops commit.

Structured reasoning — applies McKinsey-grade frameworks (5 Whys, Fishbone, First Principles, SCAMPER) with mandatory bias detection. Use for complex multi-factor problems, not simple linear analysis.

Pre-implementation red-team analysis. Use when a plan is high-risk, critical path, or expensive to reverse. Challenges plans before code is written — finds edge cases, security holes, scalability bottlenecks, error propagation risks, and integration conflicts. Catches flaws at plan time (10x cheaper than post-implementation).

Creates code-based visual assets — SVG icons, OG image HTML templates, social banners, and icon sets. Use when generating visuals as code (vector/HTML), NOT raster images — for raster generation see @rune-pro/media. Outputs files with usage instructions.

Comprehensive project audit — security, dependencies, code quality, architecture, performance, infra, docs, and mesh analytics. Use when needing a full 8-dimension health-score snapshot before a major release, M&A diligence, or quarterly review. Delegates to specialist skills (sentinel, dependency-doctor, perf, autopsy, etc.).

Full codebase health assessment. Use when diagnosing project health or starting a rescue workflow on legacy code — OR when evaluating an external GitHub repo for dependency / fork / contribution decisions (--external mode). Analyzes complexity, dependencies, dead code, tech debt, and git hotspots. Produces a health score and rescue plan.

Business Analyst agent. Use when starting a new feature requiring requirements elicitation BEFORE plan or cook. Asks probing questions, identifies hidden requirements, maps stakeholders, defines scope boundaries, and produces a structured Requirements Document that plan and cook consume.

11 hooks across 6 events