メニュー
일관된 커밋 메시지 작성을 위한 컨벤션 가이드를 실행합니다.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | commit-msg |
| description | 일관된 커밋 메시지 작성을 위한 컨벤션 가이드를 실행합니다. |
| user-invocable | true |
일관된 커밋 메시지 작성을 위한 컨벤션 가이드를 실행합니다.
<type>(<scope>): <subject>
<body>
<footer>
| Type | 설명 | 예시 |
|---|---|---|
feat | 새로운 기능 | 로그인 기능 추가 |
fix | 버그 수정 | 로그인 오류 수정 |
docs | 문서 변경 | README 업데이트 |
style | 코드 스타일 (포맷팅) | 들여쓰기 수정 |
refactor | 리팩토링 | 함수 분리 |
perf | 성능 개선 | 쿼리 최적화 |
test | 테스트 추가/수정 | 단위 테스트 추가 |
build | 빌드 시스템 | webpack 설정 |
ci | CI 설정 | GitHub Actions |
chore | 기타 작업 | 의존성 업데이트 |
revert | 커밋 되돌리기 | feat 커밋 롤백 |
# 이슈 참조
Refs: #123
Closes: #456
# Breaking Change
BREAKING CHANGE: 설명
feat(auth): add OAuth2 login with Google
- Implement Google OAuth2 authentication flow
- Add callback handling for token exchange
- Store refresh tokens securely
Refs: #123
fix(cart): resolve race condition in quantity update
When rapidly clicking +/- buttons, the cart quantity
would sometimes show incorrect values due to stale state.
Fixed by implementing optimistic locking.
Closes: #456
refactor(user): extract validation logic to separate module
Move user validation functions from UserService to
dedicated UserValidator class for better testability.
No functional changes.
feat(api)!: change response format to JSON:API spec
BREAKING CHANGE: API responses now follow JSON:API
specification. Clients need to update response parsing.
Migration guide: docs/migration-v2.md
변경사항 분석 후 커밋 메시지 제안:
## Suggested Commit Message
feat(module): brief description
Refs: #issue
### Alternative Options
1. `fix(module): ...` - if this is a bug fix
2. `refactor(module): ...` - if no functional change
변경된 파일들을 분석하여 적절한 커밋 메시지를 제안하세요.
Interactive requirements discovery through Socratic dialogue and systematic exploration
사용자 계획을 기존 도메인 모델에 대해 stress-test하는 인터뷰 세션. 용어를 날카롭게 다듬고, 결정이 굳어질 때마다 CONTEXT.md(도메인 어휘 사전)와 ADR을 인라인으로 갱신한다. 새 기능 요구사항 탐색은 `/brainstorm`을, 기존 도메인 모델·용어와의 정합성 점검은 이 스킬을 사용한다.
Evaluate design from a UX perspective, assessing visual hierarchy, information architecture, emotional resonance, cognitive load, and overall quality with quantitative scoring, persona-based testing, automated anti-pattern detection, and actionable feedback. Use when the user asks to review, critique, evaluate, or give feedback on a design or component.
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review. (Impeccable design audit — distinct from /audit which validates project rules.)
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system.
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks