Explore skills
65,415 skills found
graphviz-docs-compiler
Compile Graphviz diagrams (.dot files) to SVG in-place. Use when working with .dot files or markdown with Graphviz code blocks, or when user says "compile diagrams", "generate SVG from dot files", "update documentation diagrams".
skill-lint
Lint a BDK skill or agent file for best practices and portability. Use when reviewing, creating, or editing a skill (skills/*.md) or agent (agents/*.md) to verify it meets BDK conventions. Trigger on phrases like "check this skill", "verify agent", "does this follow best practices", "lint skill", or when about to commit a new skill/agent.
review-full
Smart review dispatcher. Auto-detects scope from diff (frontend/backend/docs/both), runs the right fix loops until all gates pass. Used as Phase R entry point in /ship.
create-plan
Create comprehensive implementation plan with exploration and trade-off analysis
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\"
execute-plan
Execute an implementation plan, then run tests and static analysis, fixing issues
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.