Loading...
Loading...
Found 158 Skills
Unified Entry for Godot Skills, which intelligently selects and invokes the most suitable Godot sub-skills based on user needs, providing a one-stop development experience with 15 professional skills
Review and clean up low-quality code comments. Use when you notice "what" comments that should be "why" comments, or want to clean up comment noise before a PR.
Document project tools and CLI utilities in docs/define/tools/. Use when documenting internal CLIs, scripts, development tools, or third-party integrations that team members need to understand and use.
Manage logical workspaces for organizing development across multiple organizations/contexts. Use when: (1) Creating a new workspace for a project/org, (2) Listing available workspaces, (3) Switching active workspace, (4) Configuring workspace-specific settings (GitHub/JIRA tokens, work directory). Workspaces isolate configuration so you can work on personal projects vs work projects without conflicts.
Opens a jackin❯ feature or idea as a roadmap item draft plus an early PR; never writes code.
Game development tools, asset pipelines, version control, build systems, and team development workflows for efficient production.
Fetch project statistics from SpecStory Cloud. Run when user says "get project stats", "show SpecStory stats", "project statistics", "how many sessions", or "SpecStory metrics".
Create standalone debugging interfaces that reveal the internal workings of complex systems through interactive visualization. Use when the user wants to understand how something works, debug internal state, visualize data flow, see what happens when they interact with the system, or build a debug panel for any complex mechanism. Triggers on requests like "I don't understand how this works", "show me what's happening", "visualize the state machine", "build a debug view for this", "help me see the data flow", "make this transparent", or any request to understand, debug, or visualize internal system behavior. Applies to state machines, rendering systems, event flows, algorithms, animations, data pipelines, CSS calculations, database queries, or any system with non-obvious internal workings.
Use the @steipete/oracle CLI to bundle a prompt plus the right files and get a second-model review (API or browser) for debugging, refactors, design checks, or cross-validation.
Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.
Opens a new jackin' feature or idea as a roadmap item draft plus an early pull request, without writing any code. Use when the operator runs /jackin-dev:propose.
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.