메뉴
Quick PR creation reference
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
This skill should be used when the user needs to plan features, break down requirements, create implementation tasks, or design software architecture. Use this skill for comprehensive requirements analysis, technical planning, and creating structured task hierarchies with dependencies. The skill executes in the main conversation context.
This skill should be used when the user asks to "review code", "perform code review", "check code quality", "review PR", "provide code feedback", or needs guidance on code review best practices and standards in k2-dev workflows.
This skill should be used when the user asks to "check quality gates", "validate against standards", "read AGENTS.md", "enforce project patterns", "follow constitution.md", "validate code quality", or needs guidance on quality standards enforcement in k2-dev workflows.
This skill should be used when the user needs to create comprehensive test plans, define test cases and coverage strategies, validate test completeness, analyze ticket requirements for testing needs, or document test strategies. The skill executes in the main conversation context and provides thorough test planning guidance without implementing tests.
This skill should be used when you need to generate a comprehensive status report for a beads ticket, including summary, progress, dependencies, PR status, and next steps. Use this after workflow completion or when the user requests a ticket status report.
This skill should be used when the user asks to "work with beads tasks", "create a beads ticket", "update beads status", "read task comments", "manage dependencies", "sync beads", "use bd commands", or needs guidance on beads task management workflows. Provides comprehensive beads CLI usage and workflow patterns.
| name | PR Creation |
| description | Quick PR creation reference |
| version | 0.1.0 |
<type>: <summary> (<ticket-id>)
Types: feat, fix, refactor, docs, test, chore, perf, security
IMPORTANT: Always follow the Pull Request template in .github/pull_request_template.md if it exists.
If no template exists, use:
## Summary
Brief description of changes
## Changes
- List of changes
## Testing
- How validated
## References
- Implements: <ticket>
gh pr create --title "feat: Add feature (beads-123)" \
--body "$(cat <<'EOF'
## Summary
...
## Changes
- ...
## Testing
- ...
## References
- Implements: beads-123
EOF
)"
gh pr view --json url -q .url