Menu
Create Git commits following Flooding project conventions. Splits changes into logical units with correct type prefix and Korean description.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | commit |
| description | Create Git commits following Flooding project conventions. Splits changes into logical units with correct type prefix and Korean description. |
| allowed-tools | Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git diff:*), Bash(git log:*), Read |
Format: type : 설명
type : 설명, never type:설명feat / fix / update / add / test / docs / style / perf / refactor / merge| Type | When to use |
|---|---|
feat | New feature |
add | Add files, configs, dependencies |
fix | Bug fix |
update | Modify existing feature or review feedback |
refactor | Code restructuring without behavior change |
test | Add or modify tests |
docs | Documentation only |
style | Formatting, ktlint |
perf | Performance improvement |
merge | Merge commit |
feat : 동아리 폼 생성 API 구현
fix : 활성 폼 조회 시 NPE 수정
update : 리뷰 반영 - 폼 필드 UniqueConstraint 추가
test : 동아리 신청 서비스 단위 테스트 추가
perf : save 루프를 saveAll로 변경
style : ktlint 포맷팅 적용
git status, git diffgit addgit commit -m "message"git log --oneline -n <count>커밋 ㄱㄱ, commit 등)Creates a new git branch following the project's branch naming convention. Use this skill whenever the user wants to start new work, create a branch, switch to a new branch.
Generate PR title and body from commits since the base branch, then create the PR on GitHub following the project PR template exactly.
Check PR review comments, reflect valid feedback into code, commit, push, then reply to each comment with the resolving commit hash.
Run a structured checklist over changed files — Kotlin style, JPA/transaction correctness, naming conventions, test coverage, and security basics. Produces a ✓/⚠/✗ report.
Run KtLint formatting on all Kotlin source files via Gradle. Use when .kt files need formatting or after bulk edits.
Kotest + MockK testing patterns for this project — BehaviorSpec structure, mock creation, stubbing, argument capture, and exception assertions. Reference when writing or reviewing test code.