Explorar skills

Jobs to Be Done skills for Claude Code. Turn customer interview transcripts into structured, version-controlled demand evidence.

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

Smart commit + push + auto-create PR. Blocks push to main. Runs pre-flight gate checks before pushing.

Verify Phase D doc updates are accurate. Binary pass/fail gate — checks stat accuracy, file path validity, code-doc sync, completeness. Runs after /update-docs.

Automated UX review → fix → re-review loop. Target is perfection (10/10). Fixes ALL severities including Suggestions — because UX polish compounds.

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.

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.

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 an implementation plan, then run tests and static analysis, fixing issues

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

Propose better object-oriented architecture for complex, procedural code