Paddock

Interact with Paddock — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via Paddock APIs.

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Claude AskUserQuestion rendering for speckit checklist.

Claude AskUserQuestion rendering for speckit clarify.

Create or update the feature specification from a natural language feature description.

Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.

Generate a custom checklist for the current feature based on user requirements.

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

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 is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"

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"

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

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

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"

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

Detect Git remote URL for GitHub integration

General code quality review — project guideline compliance, bug detection, code quality analysis.

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

Error handling review — silent failure detection, catch block analysis, error logging.

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.

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"

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

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

Run a full project health diagnostic — checks structure, agents, features, scripts, extensions, and git status.

Detect Git remote URL for GitHub integration

General code quality review — project guideline compliance, bug detection, code quality analysis.

Code comment accuracy verification, documentation completeness assessment, comment rot detection.

Error handling review — silent failure detection, catch block analysis, error logging.

Comprehensive code review using specialized agents — orchestrates code, comments, tests, errors, types, and simplify agents sequentially.

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

Test coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.

Type design analysis — encapsulation, invariant expression, usefulness, and enforcement.

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Post-implementation quality gate that reviews changes, fixes small issues (scout rule), creates tasks for medium issues, and generates analysis for large issues.

Skill for the Adapters area of paddock. 108 symbols across 22 files.

Skill for the Chat area of paddock. 62 symbols across 10 files.