Loading...
Loading...
Found 56 Skills
AI-Native Issue-Driven development workflow. From GitHub Issue to merged PR: parse issue, explore codebase, design technical plan, execute with agent team, create PR, and cleanup. Use when a user wants to implement a GitHub Issue end-to-end: `/issue-flow #123` or `/issue-flow` to pick from open issues.
This skill should be used when the user asks to "generate an AGENTS.md", "create a CLAUDE.md", "write agent instructions", "set up AGENTS.md", "make an AGENTS.md for this repo", "configure agent behavior", or mentions generating, writing, or improving an AGENTS.md or CLAUDE.md file for a project.
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 — Deep codebase exploration with parallel agents. Use when exploring a repo or discovering architecture.
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".
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.
Navigate unfamiliar code using GitNexus knowledge graph
Multi-repository codebase exploration for library internals, architecture understanding, and implementation comparisons.
Explores codebase to find patterns, similar features, and constraints
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.
Continuously interview users around a plan or design until a shared understanding is reached, and address each branch of the decision tree one by one. Use this when the user wants to stress-test a plan, have their design grilled, or mentions "grill me".