All Skills

Skill for the Layout area of paddock. 55 symbols across 15 files.

Skill for the Panels area of paddock. 727 symbols across 76 files.

Skill for the _shared area of paddock. 33 symbols across 6 files.

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

Speckit Implement

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

Detect Git remote URL for GitHub integration

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

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

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

Create a feature branch with sequential or timestamp numbering

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

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

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

Validate current branch follows feature branch naming conventions

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

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"

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

Initialize a Git repository with an initial commit

Skill for the Observability area of paddock. 105 symbols across 26 files.

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

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

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"

Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.

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

Applies Go rules for packages, explicit errors, interfaces, concurrency, tests, and tooling.

Applies C/C++ rules for resource safety, ownership, ABI, builds, tests, and validation.

Applies ESP32 rules for GPIO, boot states, relays, sensors, connectivity, firmware safety, and validation.

Routes rendered UI testing, visual regression, browser QA, accessibility, responsive, performance, or frontend review to a leaf skill.

Implements security-sensitive changes with conservative trust boundaries, secret protection, tests, and verification.

Routes UI implementation or redesign to the narrowest build workflow for pages, apps, dashboards, and styled frontends.

Routes Figma creation, editing, inspection, connection, components, or motion to the matching Figma workflow.

Routes ambiguous multi-stage UI work across research, concept, Figma, implementation, and QA. Do not use for a clear leaf task.

Applies TypeScript/JavaScript rules for types, async behavior, APIs, tooling, tests, and architecture.

Plans parallel agents or worktrees with isolated ownership, validation lanes, and merge rules. Use only for safely separable work.