Loading...
Loading...
Found 137 Skills
Create a PRD from current context, then break it into tracer-bullet issues and publish everything to the project issue tracker. Use when user wants end-to-end issue creation from a plan, idea, or requirement.
Multi-agent PR and code review workflow for projects using multiple AI assistants (Claude, GitHub Copilot/Codex, Gemini Code Assist). Use when working with pull requests, code reviews, commits, or addressing review feedback. Teaches how to check all feedback sources (conversation, inline, reviews), respond to inline bot comments, create Fix Reports, and coordinate between agents that use different comment formats. Critical for ensuring no feedback is missed from external review bots.
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
Git 설정부터 PR까지의 전체 진행 상황을 체크리스트로 보여주고 현재 단계를 안내합니다. "어디까지 했지?", "진행 상황", "다음 단계" 같은 질문에 사용됩니다.
Git 설정부터 PR 생성까지 전 과정을 자동으로 실행합니다. "자동으로 해줘", "전부 자동화", "원클릭 PR", "자동 설정" 같은 요청에 사용됩니다.
Clean up local branches after PR merges. Syncs main with origin, identifies branches with merged PRs, and proposes safe deletion. Use when the user asks to 'clean up branches', 'delete merged branches', 'sync branches', or mentions branch cleanup.
Create a PR from current commits and/or local changes. Identifies base branch, creates topic branch if needed, commits changes, and opens a PR.
Create a high-quality pull request: branch, focused changes, lint/build, conventional commit, and a clear PR description with validation steps. Use when the user asks to open or prepare a PR.
Fix GitHub Actions CI failures using GitHub CLI (gh): inspect runs/logs, identify root cause, patch workflows/code, rerun jobs, and summarize verification. Use when GitHub Actions CI is failing or needs diagnosis.
This is used to review comments on an active pull request and decide whether to accept, iterate, or reject the changes suggested in each comment.
This skill should be used when a QA engineer wants to test or verify a completed task, run through acceptance criteria, check Gherkin scenarios against the implementation, record pass/fail results, or sign off on a ticket before merge. Triggers on phrases like "verify task
Use when new insights change the scope, acceptance criteria, domain language, or technical constraints of an existing Epic, Feature, or Task — for example "refine epic