pr
Create pull requests for reviews
Manually creating pull requests wastes time and risks inconsistent formatting. This skill automates PR creation for specification and implementation reviews with proper templates, title conventions, and user confirmation before execution.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"pr" ์ฌ์ฉ ์ค์ ๋๋ค. /pr type=impl
์์ ๊ฒฐ๊ณผ:
- Current branch: impl/001-01-01-user-auth
- Title: impl: ใฆใผใถใผ่ช่จผๆฉ่ฝใฎๅฎ่ฃ
- Base: main
- Summary: 001-01-01 ใๅฎ่ฃ , ใญใฐใคใณ/ใญใฐใขใฆใๆฉ่ฝ
- Test plan: ๅ จACใฎใในใใ้้
- PR URL: https://github.com/user/repo/pull/123
"pr" ์ฌ์ฉ ์ค์ ๋๋ค. /pr type=spec
์์ ๊ฒฐ๊ณผ:
- Current branch: spec/002-01-03-payment
- Title: spec: ๆฏๆใๆฉ่ฝใฎไปๆจฃ็ญๅฎ
- Base: main
- Summary: 002-01-03 ใฎไปๆงใ็ญๅฎ
- Review items: User story, EARS format, dependencies, scope
- PR URL: https://github.com/user/repo/pull/456
๋ณด์ ๊ฐ์ฌ
์์ This skill consists of a single SKILL.md documentation file with no executable code. All 51 static findings are false positives: markdown code blocks were misidentified as backtick execution, workflow strings like 'action-id' and '{AC2}' as C2 keywords, and GitHub URLs as hardcoded network endpoints. The file contains only documentation describing PR creation workflows.
์ํ ์์ธ
๐ ๋คํธ์ํฌ ์ ๊ทผ (6)
๐ ํ์ผ ์์คํ ์ก์ธ์ค (1)
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (32)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Automated spec review PRs
Automatically create PRs when specification drafting completes with proper review checklists
Implementation review PRs
Generate standardized implementation PRs after completing all AC-verified tasks
Consistent PR documentation
Ensure every PR includes summary, test plan, and AC confirmation fields
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
/pr
/pr type=spec
/pr type=impl action-id=001-01-01
/pr type=impl base=develop
๋ชจ๋ฒ ์ฌ๋ก
- Always confirm PR details before approval to catch errors early
- Use consistent title prefixes to distinguish spec from implementation PRs
- Run tests locally before creating implementation PRs to avoid CI failures
ํผํ๊ธฐ
- Skipping user confirmation step when in a hurry
- Creating PRs without verifying tests pass first
- Using inconsistent naming conventions across different PRs
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
What tools are required for this skill?
Can I create PRs for non-GitHub repositories?
What happens if tests are failing?
Is my data safe when using this skill?
What if a PR already exists for my branch?
How is this different from GitHub's default PR creation?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
Clionegohan๋ผ์ด์ ์ค
MIT
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/Clionegohan/YoRuH-Resonance-Archive-C4-Sync-/tree/main/atdd-sdd/.claude/skills/pr์ฐธ์กฐ
main
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md