20,421 skills sorted by stars.
**ALWAYS USE THIS SKILL** when asked to review a PR or given a PR URL. Provides systematic workflow for code review.
Fetch and analyze GitHub PR review comments and code-level feedback using the prc CLI. Use this skill whenever the user mentions P...
Extract and summarize review comments from GitHub PRs. Use when analyzing PR reviews, checking unresolved issues, or responding to...
Create GitHub PRs with gh, fetch review comments, fix them commit-by-commit, and reply to each comment individually with correctly...
プルリクエストのレビューコメントに体系的に対応するスキル。未解決コメントを取得し、問題を分析し、修正案を提案し、コメント単位でコミットを作成し、手動での返信とresolveをガイドします。GitHubのPRレビューに構造化された整理された対応が必要な場合に使用...
Create pull requests with an interactive review and approval step. Use this skill when the user asks to create a pull request, ope...
Review pull requests by integrating GitHub operations with Linear issue tracking. Use when: (1) Validating PR changes against Line...
Manage the PR review feedback loop: monitor CI checks, fetch review comments, and iterate on fixes.Use when: (1) pushing changes t...
Use when creating PRs to enforce code quality standards. Automated detection of anti-patterns, security issues, and code smells. P...
Comprehensive GitHub Pull Request code review skill. Use when asked to "review this PR", "code review", "review pull request", "ch...
Capture and document UI changes with before/after screenshots for pull requests. Use when creating PRs that include visual changes...
Automatically submit pull requests with full autonomous workflow. Use when the user mentions creating a PR, submitting a PR, mergi...
Use when writing Pull Request titles or commit messages to follow the Korean action word convention.
File Linear tickets from PR review feedback and notify the PR author. Use when asked to file a ticket from PR comments, create a t...
Context-efficient PR comment triage. Evaluate, decide, act. Fix important issues, resolve the rest silently.
Update existing pull request title and description based on latest changes.Use when user wants to refresh PR with latest commits....
Spawn a Claude worker to address PR feedback, fix CI failures, or continue work on a pull request. Use when a PR needs updates bas...
This skill should be used when the user asks to "create a PR", "open a pull request","write a PR description", "push and create PR...
This skill should be used when redesigning golf practice station pages (driving range, short game, putting) to be goal-oriented an...
Use this skill for early-stage project planning through Product Requirements Documents (PRDs). Guides users from initial project i...
Product Requirements Document creation and feature specification writing. Use when writing PRDs, technical specs, feature document...
Systematic PRD-driven software development workflow for Claude Code. Use when the user wants to (1) Import/parse feature bundles i...
Transform project ideas into requirements documentation focusing on user outcomes and functionality, not implementation. Use when...
PRD (Product Requirements Document) formatting skill for Linear issues. Use when creating or updating Linear issues to ensure cons...
Rigorous engineering planning and PRD implementation standards. Use when creating implementation plans, working through PRD phases...
Implement PRDs/specs with a mandatory precheck review before coding. Use when a user asks to implement a PRD/feature spec/requirem...
Automatic PRD lifecycle management, organization, and status tracking. Use when working with Product Requirements Documents (PRDs)...
Creates PRDs using persistent file-based planning. Use when user explicitly says "PRD", "product requirements document", or "产品需求文...
Complete PRD (Product Requirements Document) creation workflow that guides users from initial idea to implementation-ready specifi...
PRD, 기획서, 요구사항, 제품 기획, MVP, 제품 전략 - Use when brainstorming product ideas, creating PRD documents, defining MVP scope, or planning...
Master PRD templates including problem statements, success metrics, requirements, user stories, and technical considerations. Use...
Transform PRDs (Product Requirements Documents) into structured XML app specifications optimized for AI coding agents. Converts de...
Generates production-grade TaskMaster tasks.json from Product Requirements Documents (PRD). Activates via codeword [ACTIVATE:PRD_T...
PRD(요구사항)를 분석하여 테스트 케이스를 도출합니다. TDD의 시작점으로, 구현 전에 테스트 시나리오를 정의합니다. Inside-Out TDD 접근법 적용.
Write comprehensive Product Requirements Documents (PRDs)
Pre-commit validation checklist before staging and committing code. Use BEFORE every git commit to ensure code quality, tests pass...
MANDATORY setup for all projects. Automated code quality enforcement before commits. Prevents bad code from entering repository.
ADVISORY validation of code against design principles that linters cannot enforce. Use after linter passes and tests pass to valid...
Verifica que no haya credenciales, secrets o archivos sensibles antes de pushear a GitHub. Busca API keys hardcodeadas, .env con v...
Gate 4: API contracts document - defines component interfaces and data contractsbefore protocol/technology selection. Large Track...
Gate 5: Data structures document - defines entities, relationships, and ownershipbefore database technology selection. Large Track...
Gate 6: Technology choices document - explicit, versioned, validated technologyselections with justifications. Large Track only. H...
Gate 2: Feature relationship map - visualizes feature landscape, groupings,and interactions at business level before technical arc...
Gate 1: Business requirements document - defines WHAT/WHY before HOW.Creates PRD with problem definition, user stories, success me...
Gate 0 research phase for pre-dev workflow. Dispatches 3 parallel research agentsto gather codebase patterns, external best practi...
Gate 8: Zero-context implementation steps - 2-5 minute atomic subtasks withcomplete code, exact commands, TDD pattern. Large Track...
Gate 7: Implementation tasks - value-driven decomposition into working incrementsthat deliver measurable user value.