Explorar skills

Branch-aware audit orchestrator. On main — scans whole project, opens tracker issue. On feature branch — scopes to diff, auto-fixes, stages changes.

Find cross-interview patterns across 3+ switch analyses in .jtbd/switches/. Clusters recurring jobs, identifies force patterns, surfaces evidence gaps, and generates actionable recommendations. Outputs structured YAML to .jtbd/patterns/. Use when: "find patterns", "jtbd patterns", "cross-interview", "what are the jobs".

Merge current PR after CI passes. Waits for all checks, squash merges, deletes branch, switches to main.

Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"

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.

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\"

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\"

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?\"

Update the docs/architecture .md spec files after adding a new feature, without re-running the full ms-spec. Detects what changed via git diff, maps changes to the right spec sections, grills the developer for missing context, and patches only the affected .md files. Use when a feature is done and the user wants to keep AI agent context up to date, or says "update spec", "sync spec", "ms-spec-upda

Create structured GitHub issues via gh CLI using type-specific templates (bug, feat, refactor, doc, perf, security). Use when filing bugs, requesting features, tracking work, opening tickets, or any intent to create a GitHub issue — even implicit phrases like "track this" or "file this".

Manually-triggered comprehensive codebase health audit covering security, architecture, documentation drift, dead code, and test coverage gaps. Produces a ranked markdown report, files prioritized GitHub issues, and proposes (but never autonomously opens) auto-fix PRs for trivial safe changes. Use when the user wants to audit, scan, review the health of, do a security check on, find dead code in,

Use when the user wants to prevent broken code from being pushed, block git push when tests fail, run tests before push, set up push protection, or add a safety net against pushing untested code. Covers any request to gate pushes on test results — whether they mention "hook", "pre-push", or just describe wanting to stop bad code from reaching the remote. Also handles auto-fix/auto-repair of test f