MUST use this skill when user asks to create PR, open pull request, submit for review, or mentions "PR 생성/만들기". This skill OVERRIDES default PR creation behavior. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels.
/plugin marketplace add Bae-ChangHyun/cc-plugins-bch/plugin install gitwf@cc-plugins-bchThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Creates Pull Requests with task validation, test execution, and Conventional Commits formatting.
# 1. Verify GitHub CLI
gh --version && gh auth status
# 2. Gather information
git log develop..HEAD --oneline
git diff develop --stat
git rev-parse --abbrev-ref HEAD
# 3. Run project tests
make test # or: pytest, npm test
# 4. Create PR
gh pr create --title "..." --body "..." --base develop --label feature
gh --version && gh auth status
If not installed: brew install gh then gh auth login
Always ask user:
I'm about to create a PR from [current-branch] to [target-branch]. Is this correct?
- feature branch → develop (90% of cases)
- develop → master/main (releases)
# Current branch
git rev-parse --abbrev-ref HEAD
# Commits since base branch
git log [base-branch]..HEAD --oneline
# Files changed
git diff [base-branch] --stat
# Remote tracking status
git status -sb
Look for task files in these locations:
.kiro/specs/*/tasks.mddocs/specs/*/tasks.mdspecs/*/tasks.mdtasks.md in project rootFor each commit, identify:
task X.Y, Task X, #X.Y patternsBREAKING CHANGE in bodyDetect and run project tests:
make testnpm testpytestTests MUST pass before creating PR.
| Branch Flow | PR Type | Title Prefix |
|---|---|---|
| feature/* → develop | Feature | feat(scope): |
| fix/* → develop | Bugfix | fix(scope): |
| hotfix/* → main | Hotfix | hotfix(scope): |
| develop → main | Release | release: |
| refactor/* → develop | Refactoring | refactor(scope): |
Title format: <type>(<scope>): <description>
Body structure:
## Summary
- Key change 1
- Key change 2
## Changes
- List of specific changes
## Test Plan
- [ ] Unit tests passing
- [ ] Integration tests passing
- [ ] Manual testing done
## Related
- Refs: Task N, Issue #X
| Commit Type | Labels |
|---|---|
| feat | feature, enhancement |
| fix | bug, bugfix |
| refactor | refactoring, tech-debt |
| docs | documentation |
| ci | ci/cd |
| security | security |
Check available labels: gh label list
Show content to user first, then:
gh pr create --title "[title]" --body "$(cat <<'EOF'
[body content]
EOF
)" --base [base_branch] --label [labels]
Before generating PR, ensure you have:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.