Loading...
Loading...
Found 10,137 Skills
Debug Streamlit frontend and backend changes using make debug with hot-reload. Use when testing code changes, investigating bugs, checking UI behavior, or needing screenshots of the running app.
Create a git commit following the Conventional Commits specification.
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
Comprehensive codebase research skill. Documents codebase as-is by spawning parallel sub-agents and synthesizing findings into research documents.
Help initialize and validate a Stac-enabled Flutter project and ship a first server-driven screen. Use when users ask to set up Stac CLI, run stac init/build/deploy, verify project prerequisites, or troubleshoot first-run setup and missing configuration files.
Core n8n automation software using n8n-MCP tools.
Use when coordinating software development projects requiring multiple specialists (architect, developers, mathematician, statistician, notebook-writer) with quality gates for archival setup, requirements, architecture, pre-mortem, code review, testing, and version control integration.
Interactive planning and execution for complex tasks. Use when user asks to use or invoke planner skill.
Procedures for updating the base version of GitHub Spec Kit (https://github.com/github/spec-kit) and synchronizing templates/scripts. This is used when you need to update Spec Kit, apply differences from upstream releases, incorporate templates/commands/scripts, and maintain local operations (Japanese localization, no branch operations, SPEC-[8-digit UUID])
Linear ticket lifecycle for any project. Use when starting work on a Linear issue, ending work on an issue, or asking what to work on next. Triggers: start KAT-N, pick up, implement, finish, complete, done with, close, what's next, next ticket, next issue. Handles blocker validation, status transitions, context loading, branch creation, evidence gating, and chain promotion.
Design PM-friendly technical architecture for features. No code, only high-level design decisions.
Use when research direction needs assessment, critical knowledge gaps must be identified, or priorities must be recommended based on impact, dependencies, and effort (especially at project milestones or when scope questions arise)