Loading...
Loading...
Found 2,777 Skills
Use when generating multiple curriculum-aligned concept files in parallel (5+ concepts) - researches curriculum, creates concept list, spawns parallel generation agents, orchestrates review loop until all pass
Provides spec writing guidelines with 6 core areas and boundary system. Use when writing SPEC.md, defining requirements, creating project specifications, 요구사항 정의, or 스펙 작성.
Review PR comments, discuss improvements, and reply with resolution status
Orchestrate full development workflow. Use when implementing features, starting structured development, or user mentions "workflow" or "implement issues".
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Pull request authoring standards — structured descriptions, linking issues, providing test evidence, and writing good summaries. Reference when creating or describing pull requests.
Analyze how code changed over time. Use when investigating regressions, understanding why code was written a certain way, or finding when a behavior changed.
Fetches Jira ticket context, creates a branch, and drafts an implementation plan
Stage all changes, commit, and push. Use when user asks to "ship", "commit and push", "add all and push", or requests staging all changes, committing, and pushing.
Create engaging changelogs for recent merges to main branch
Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees
Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps. Use when the user asks to "investigate this bug", "debug this", "figure out why this fails", "find the root cause", "why is this broken", "troubleshoot this", "diagnose the issue", "what's causing this error", "look into this failure", "why is this test failing", or "track down this bug".