Loading...
Loading...
Found 11 Skills
Update the title and body of one or more pull requests.
Use when preparing a pull request for merge: inspect diffs, collect checks and review comments, classify findings, fix safe issues, verify, and loop until merge-ready.
GitHub PR의 미해결 리뷰 스레드를 조회해 코멘트별로 타당성을 검증한 뒤, 적절한 지적만 골라 수정·커밋한다. 모든 리뷰어(봇·사람)의 코멘트를 처리한다. "코드 리뷰 반영해줘", "리뷰 코멘트 처리해줘", "PR 리뷰 적용해줘", "apply PR review comments", "handle review feedback", "autofix", "/autofix" 같은 요청에 활성화한다. 리뷰 코멘트를 그대로 적용하지 않고, 검증에서 적절로 판정된 것만 사용자 승인(기본) 또는 자동(`--auto`)으로 반영한다.
Automatically hunt for high-impact OSS contribution opportunities.
Multi-PR development for large features. Stack dependent PRs, manage rebases, and get faster reviews on smaller changes. Use when creating stacked PRs.
Research libraries, APIs, and patterns using searchGitHub and Exa tools. Finds real-world implementations and saves structured reports to docs/research/. Use when investigating technologies, debugging issues, or comparing options.
Survey a project read-only — git working tree, GitHub issues and their declared priority, open PRs, unfiled plans — into a one-screen dashboard that crowns one finish-first next move routed to the kit that does it, saved by default as a throwaway snapshot under docs/status/. Use when you sit down at a project and ask "what should I do next", "check project status", "what's next", "what's most important right now", "orient me", "write me a status file", or run "/statuskit" — add "just print it" or "no file" to skip the snapshot.
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])
Retrospective audit of recently merged/closed PRs for anomalies that slipped through - merges without green builds, merges onto red main, unresolved or post-merge review threads, hollow resolutions. Read-only sweep, then confirmed remediation (issues, disposition replies). Use when asked to sweep PRs, audit merged PRs, or check what slipped through.
Discover valuable GitHub fork divergence beyond stars. TRIGGERS - fork analysis, fork intelligence, find forks, valuable forks, fork divergence, fork discovery, upstream forks.
Use when converting a new GitHub issue into a structured PRD, or posting clarifying questions when the issue is underspecified.