Explore skills
65,337 skills found
bdk-rules-design-patterns
Design pattern principles (GoF, anti-patterns, pattern documentation). Preloaded into agents that propose or review code structure; not user-facing.
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\"
bdk-rules-architecture
Architecture principles (layering, boundaries, dependency direction). Preloaded into agents that reason about structure; not user-facing.
bdk-tier-review
Tool-tier guidance for code review (change detection, risk scoring, review context). Preloaded into reviewer subagents; not user-facing.
bdk-rules-code-quality
Code-quality principles (language-agnostic). Preloaded into agents that write or review code; not user-facing.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\"
refactor
Propose better object-oriented architecture for complex, procedural code
save-progress
Save current work progress to .bdk/save-progress/ for resuming in a future session. Use when context is large, work is in progress, and you want to stop and continue later.
update-docs
Use when existing architecture documentation needs refreshing after code changes, when running periodic doc maintenance, or when user asks to "update docs", "refresh documentation", or "sync docs with code".
restore-progress
Restore saved work progress from .bdk/save-progress/ to resume a previous session. Loads referenced plans, creates TaskList items for remaining work.
gitnexus-guide
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\"