Loading...
Loading...
Found 58 Skills
Use when discovering codebase facts, context, patterns, constraints, or unknowns through focused, incremental, read-only investigation without diagnosing a failure or modifying state.
Guided project onboarding for new codebases. Helps agents understand project structure, build systems, test commands, and development workflows by creating persistent knowledge memories.
Interview user to clarify any topic - exploring codebase, investigating issues, planning features, understanding requirements, or drilling into plans. Socratic questioning to uncover details.
Before searching a codebase, forces you to zero in on the target: what exactly are you looking for, what would it look like, where would it live, what else might it be called. Activates on "find", "where is", "search for", or when exploration begins. Prevents grep-and-pray.
Explore a codebase with parallel Haiku agents. Modes - --fast (1 agent), default (3), --deep (5). Use when user says "learn [repo]", "explore codebase", "study this repo".
Systematic 4-phase codebase exploration: Detect, Explore, Map, Summarize. Use when starting work on an unfamiliar codebase, onboarding to a new project, reviewing a repository for the first time, or building context before debugging or code review. Use for "explore codebase", "what does this project do", "understand architecture", or "onboard me". Do NOT use for modifying files, running applications, performance optimization, or deep domain analysis.
explore — Deep codebase exploration with parallel agents. Use when exploring a repo or discovering architecture.
Navigate unfamiliar code using GitNexus knowledge graph
Load context for a task: read the spec/ticket, explore the codebase surface, and present the task context to the user. The user controls implementation.
Specialized feature development agents. Use for deep codebase exploration and architecture design during feature development.
Context-gathering for finding files to read. Maps codebase structure, returns overview + prioritized file list with line ranges. Thoroughness: quick for lookups, medium for bugs/features, thorough for multi-area, very-thorough for architecture audits. Triggers: explore, find files, where is, how does X work.
Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when the mission demands. Use when fixing bugs, implementing features, refactoring, investigating flows, or any development task in unfamiliar territory. Triggers on "fix this", "implement this", "how does this work", "investigate this flow", "help me with this code". Do NOT use for greenfield scaffolding, CI/CD, or infrastructure provisioning.