메뉴
Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, or colorize a frontend interface. Covers websites, landing pages, dashboards, product UI, components, forms, onboarding, empty states. Handles UX review, hierarchy, accessibility, responsive behavior, theming, typography, layout, color, motion, UX copy, design tokens. Also bolder/quieter redesigns, live browser iteration, ambitious visual effects.
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Systematic development workflow: Analyze → Plan → Execute → eLicit → eXamine. Use for ANY development task: features, bug fixes, refactoring, hotfixes. Triggers: "implement", "create", "build", "fix", "add feature", "refactor", "develop". Auto-detects project type (Laravel, Next.js, React, Swift) and loads framework-specific references. Enforces: files <100 lines, interfaces separated, SOLID principles, expert self-review, sniper validation.
Use when user requests creative work - creating features, building components, adding functionality, or modifying behavior. Activates BEFORE APEX Analyze phase to refine requirements through structured questioning.
Code quality validation with linters, SOLID principles, DRY detection, error detection, and architecture compliance across all languages.
Auto-review skill for expert agents. After coding, expert applies elicitation techniques to self-correct before sniper validation. Inspired by BMAD-METHOD.
| name | commit-detection |
| description | Detects optimal commit type from git changes. Use when analyzing commits, determining commit type, or before committing. |
Expert knowledge for detecting the optimal conventional commit type.
# Get modified files
git diff --name-only
git diff --staged --name-only
# Get change statistics
git diff --stat
git diff --staged --stat
# Check for keywords in diff
git diff | grep -i "fix\|bug\|error" | head -5
| Category | File Patterns |
|---|---|
| docs | *.md, *.txt, *.rst, README*, CHANGELOG* |
| test | *.test.*, *.spec.*, __tests__/*, test/* |
| config | *.json, *.yml, *.yaml, *.toml, .*rc |
| ci | .github/*, .gitlab-ci.yml, Jenkinsfile |
| build | package.json, Makefile, webpack.*, vite.* |
| style | Only whitespace, formatting changes |
| src | *.ts, *.js, *.py, *.go, *.rs, etc. |
IF only docs files changed:
→ docs
IF only test files changed:
→ test
IF only config/build files changed:
→ chore
IF only CI files changed:
→ ci
IF diff contains "fix", "bug", "error", "issue", "resolve":
→ fix
IF new files added with business logic:
→ feat
IF files renamed/moved without logic change:
→ refactor
IF performance keywords ("optimize", "perf", "speed", "cache"):
→ perf
IF formatting only (whitespace, semicolons):
→ style
DEFAULT:
→ Use /commit-pro:commit for smart analysis
Extract scope from primary directory:
src/components/Button.tsx → ui or button
src/api/auth.ts → auth
lib/utils/date.ts → utils
server/routes/user.ts → user
| Type | When | Version Bump |
|---|---|---|
feat | New functionality | PATCH |
fix | Bug correction | PATCH |
docs | Documentation only | PATCH |
style | Formatting only | PATCH |
refactor | Code restructure | PATCH |
perf | Performance | PATCH |
test | Tests only | PATCH |
build | Build/deps | PATCH |
ci | CI/CD config | PATCH |
chore | Maintenance | PATCH |
MINOR/MAJOR bumps are manual user decisions, never automatic.
See the post-commit skill for universal CHANGELOG, version bump, and tag logic (works for all repos).
Example 1: Only README changed
Files: README.md
→ /commit-pro:docs
Example 2: New component + test
Files: src/Button.tsx, src/Button.test.tsx
→ /commit-pro:feat (primary is new feature)
Example 3: Fix in existing file
Files: src/api/auth.ts
Diff contains: "fix login bug"
→ /commit-pro:fix