racecraft-lab
- 120 skills
- 0 followers
- 11 repo stars
- 3 weeks ago last updated
- ▌ Speckit Git Validate · racecraft-labValidate current branch follows feature branch naming conventions
- ▌ Speckit Review Tests · racecraft-labTest coverage quality analysis — behavioral coverage, critical gap identification, test resilience evaluation.
- ▌ Speckit Review Types · racecraft-labType design analysis — encapsulation, invariant expression, usefulness, and enforcement.
- ▌ Speckit Verify Tasks · racecraft-labVerify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
- ▌ Gitnexus CLI · racecraft-labUse 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"
- ▌ Speckit Review Errors · racecraft-labError handling review — silent failure detection, catch block analysis, error logging.
- ▌ Speckit Taskstoissues · racecraft-labConvert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
- ▌
- ▌
- ▌ Observability · racecraft-labSkill for the Observability area of paddock. 105 symbols across 26 files.
- ▌ Gitnexus Guide · racecraft-labUse 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?"
- ▌ Speckit Review Comments · racecraft-labCode comment accuracy verification, documentation completeness assessment, comment rot detection.
- ▌ Speckit Review Simplify · racecraft-labCode simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.
- ▌ Speckit Verify Tasks Run · racecraft-labVerify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
- ▌ Gitnexus Debugging · racecraft-labUse 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"
- ▌ Gitnexus Exploring · racecraft-labUse 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"
- ▌ Workflow Contracts · racecraft-labSkill for the Workflow-contracts area of paddock. 51 symbols across 11 files.
- ▌ Gitnexus Refactoring · racecraft-labUse 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"
- ▌ Speckit Retrospective Analyze · racecraft-labPerform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.
- ▌ Gitnexus Impact Analysis · racecraft-labUse 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?"