메뉴
Use when local changes pass A-E quality checks, lessons-learned review, and are under 500 lines of production code, ready for gh pr create.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| description | Use when local changes pass A-E quality checks, lessons-learned review, and are under 500 lines of production code, ready for gh pr create. |
| name | create-pr |
| trigger | PR 생성, 풀 리퀘스트 만들기, push and create PR, gh pr create, 브랜치 만들고 PR, PR 올리기, create pull request, make PR, ship code, PR 생성 및 푸시, 브랜치 분기 후 PR, PR quality check, submit PR, raise PR, 브랜치부터 PR 까지, 코드 푸시 후 PR, open pull request, submit pull request, ship to review, 이슈 연동 PR, 커밋 후 PR, PR 템플릿 생성, 자가 점검 후 PR, 품질 게이트 통과 PR, HXSK 컨텍스트 PR, PR 크기 분리 후 생성, 브랜치 생성 및 PR, git push and pr, create pr from branch, pr with quality check, submit code for review |
lessons-learned 조회 및 자가 점검 완료 여부 확인NO PR CREATION WITHOUT BRANCH CREATION FROM MAIN FIRST NO PR CREATION WITHOUT PASSING SELF-QUALITY CHECKS FIRST NO PR CREATION WITHOUT SPLITTING CHANGES (>500 LINES) FIRST NO PUSH WITHOUT RUNNING PRE-COMMIT CHECKS FIRST NO MERGE WITHOUT PLAN-IMPLEMENTATION CONSISTENCY FIRST NO PR CREATION WITHOUT ISSUE NUMBER IN TITLE FIRST NO PR CREATION WITHOUT MANDATORY BODY SECTIONS (SUMMARY, CHANGES, TEST PLAN, HXSK CONTEXT) FIRST NO PR CREATION WITHOUT LESSONS-LEARNED REVIEW FIRST NO COMMIT WITHOUT CONVENTIONAL EMOJI STYLE FIRST
git status # Working tree state
git branch --show-current # Current branch
git log --oneline -10 # Recent commits
git diff --stat # Unstaged changes
git diff --cached --stat # Staged changes
If on main branch, create a feature branch:
# Branch naming: <type>/<short-description>
git checkout -b feat/add-user-auth
Branch naming conventions:
feature/{issue-number}-{description} — New featuresbugfix/{issue-number}-{description} — Bug fixesrefactor/{issue-number}-{description} — Refactoringdocs/{issue-number}-{description} — Documentationrelease/v{version} — Release preparationFor HXSK phases (이슈 없는 경우):
feat/<description> or phase-1/implement-auth규칙: 이슈 번호 포함 필수, 영문 소문자 + 하이픈만 사용
Use the commit skill logic to:
git push -u origin $(git branch --show-current)
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<1-3 bullet points describing the changes>
## Changes
<list of key changes with file references>
## Test Plan
- [ ] Quality checks pass (shellcheck for shell scripts)
- [ ] Manual verification completed
- [ ] <specific manual verification steps>
## HXSK Context
- Phase: <N>
- Plans: <list of completed plans>
- SPEC reference: `.hxsk/SPEC.md`
EOF
)"
Follow conventional commit style:
feat(auth): add JWT-based authentication
fix(api): resolve race condition in connection pool
refactor(models): extract validation into shared module
Keep under 70 characters.
| 크기 | 프로덕션 코드 | 기준 |
|---|---|---|
| Small | ~200 lines | 목표 |
| Medium | ~500 lines | 허용 |
| Large | ~1,000 lines | 분리 검토 |
| XLarge | 1,000+ lines | 반드시 분리 |
먼저 lessons-learned 조회:
bash .hxsk/hooks/md-recall-memory.sh "pr quality check lessons-learned" \
"." 10 compact
A. 코드 ↔ 문서 정합
B. 테스트 품질
_ prefix 또는 제거됨C. 상태 동기화 / 의미론
D. Resource / Lifecycle
E. Forward-compat
실패 항목 발견 시: 수정 → 재검증 → 전 항목 통과 후 PR 생성.
| 상황 | 방식 |
|---|---|
| feature/bugfix → develop | Squash and merge |
| develop → main (릴리즈) | Merge commit |
| hotfix → main | Merge commit |
상세 컨벤션:
.hxsk/docs/CONVENTIONS.md섹션 5 참조
When a PR spans multiple HXSK plans:
## HXSK Context
- Phase 1, Plans 1-3: User authentication
- Plan 1.1: Database schema + User model
- Plan 1.2: Login/register endpoints
- Plan 1.3: JWT middleware + route protection
After PR creation, report:
PR_CREATED: #<number>
URL: <url>
BRANCH: <branch-name>
COMMITS: <count>
PR 본문 생성은 git 명령과 네이티브 도구로 수행:
# 커밋 로그 수집
git log --oneline origin/main..HEAD
# diff 통계
git diff --stat origin/main..HEAD
# PR 생성 (gh CLI)
gh pr create --title "{title}" --body "{body}"
Use when Ground Truth alignment finds memory contamination and the user explicitly requests scoped cleanup with /cleanse.
Use when registering, reviewing, merging, or rebuilding HXSK glossary term definitions after glossary-detect suggests a candidate or the user invokes /define.
Use when staged changes exist requiring qlty checks, logical split detection, or HXSK phase-scoped conventional commit creation.
Use when validating code for circular imports, layer violations, or design doc logic errors before merging architecture-level changes.
Use when .hxsk/.bootstrap-version is missing (fresh install) or exists (verify/update) to initialize HExoskeleton.
Use when shell scripts need linting/formatting before execution or commit to ensure code quality.