universe

Autonomous agent that performs a comprehensive codebase analysis. Use this agent when the user asks for a "full codebase overview", "help me understand this project", "codebase analysis", "onboard me to this codebase", "project deep dive", or wants a complete understanding of the project's architecture, hotspots, and key modules.

Autonomous agent that analyzes the temporal health of a codebase. Use this agent when the user asks for a "full evolution analysis", "temporal audit", "codebase evolution report", "how has this project changed", "project health over time", or wants a comprehensive assessment of how the codebase has evolved with drift detection and forecasting.

Autonomous agent that performs comprehensive instruction file analysis. Use this agent when the user asks for a "full instruction review", "deep analysis of my rules", "comprehensive CLAUDE.md audit", or wants a thorough assessment of instruction quality, adherence, and missing conventions in a single report. This agent discovers conventions, lints quality, and checks conformance, then produces a prioritized report.

Autonomous orchestrator for /orbit Standard mode. Runs MCP tools across all 5 claude-universe systems (security, tests, code, evolution, instructions) in parallel, verifies top findings by reading actual code, and synthesizes a unified dashboard. Used by /orbit when no mode keyword or when Standard mode is invoked. Expected runtime: 30-90 seconds on medium projects.

Autonomous agent that performs a comprehensive security audit of the entire project. Use this agent when the user asks for a "full security audit", "security assessment", "comprehensive security review", "audit my project for vulnerabilities", or wants a complete security evaluation with prioritized findings and remediation plan.

This skill should be used when the user asks to "check adherence", "check rule adherence", "are my rules being followed", "is Claude following my instructions", "how effective is my CLAUDE.md", "rule compliance", "instruction effectiveness", "how are my rules performing", "which rules are being violated", "audit my rules", "check my CLAUDE.md", mentions "/check-rules", or wants to know whether their coding agent instruction rules are actually being followed across Claude Code sessions.

Use when the user wants to infer reusable project conventions from existing code and turn them into instruction rules: "discover conventions", "infer rules from code", "what rules should I add", "generate rules from this codebase", or "/discover". This is for convention mining, not for checking rule adherence or explaining how a specific module works.

This skill should be used when the user asks "when did this get complicated", "why is this file so complex", "how did this evolve", "complexity history", "trace the evolution", "what happened to this code", "dissect this file", mentions "/dissect", or wants to understand how a file or function became complex by tracing its evolution through git history.

This skill should be used when the user asks "has this module drifted", "is this code still doing what it was designed for", "scope creep analysis", "architectural drift", "what was this originally for", "how has this changed over time", mentions "/drift", or wants to detect when code has quietly evolved away from its original purpose.

Use when the user wants a deep explanation of a specific file, module, or implementation flow: "explain this code", "walk me through this file", "why is this structured this way", or "/explain". Best for focused code understanding with history context, not for repo-wide architecture mapping, recent-change summaries, or generic "what happened?" requests.