메뉴
Generate commit titles and descriptions from uncommitted changes. Use when the user asks to generate a commit message, wants help writing a commit, or says 'commit', 'commit message', 'what should I commit', or similar.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Build React components in Next.js using CampusOS patterns. Use when implementing UI components, working with the App Router, styling with Tailwind CSS v4, or managing forms with react-hook-form and Zod.
Comprehensive frontend development hub — UI/UX design, React/Next.js patterns, Tailwind CSS v4, shadcn/ui components, Three.js 3D graphics, creative web experiences, data visualization, diagramming, Figma integration, accessibility, game development, scroll animations, and design systems. Use for ANY frontend task: building components, designing interfaces, styling, theming, animations, charts, responsive layouts, mobile design, or implementing design patterns.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
Generate PR titles and descriptions from commit history. Use when the user asks to generate a PR description, wants help writing a pull request, provides commit titles/messages, or says 'PR', 'pull request', 'PR description', or similar.
RESTful API patterns, request/response formatting, authentication flows, versioning for CampusOS. Use when designing API endpoints, planning request bodies, structuring error responses, or implementing authentication.
| name | commit-message-generator |
| description | Generate commit titles and descriptions from uncommitted changes. Use when the user asks to generate a commit message, wants help writing a commit, or says 'commit', 'commit message', 'what should I commit', or similar. |
Run these commands to understand what changed:
# See which files are modified, added, or deleted
git status --short
# See the full diff of staged AND unstaged changes
git diff HEAD
# If there are untracked files, list them
git ls-files --others --exclude-standard
Analyze the diff output and categorize changes into one of the Conventional Commit types:
| Type | When to Use |
|---|---|
feat | New functionality, new endpoints, new components |
fix | Bug fixes, error corrections |
docs | Documentation only changes |
test | Adding or updating tests |
chore | Dependencies, config, tooling, CI/CD |
refactor | Code restructuring without behavior change |
perf | Performance improvements |
style | Formatting, whitespace, semicolons (not CSS) |
Identify the scope based on which part of the codebase was changed:
| Scope | When to Use |
|---|---|
(frontend) | Changes in apps/frontend/ or frontend/ |
(backend) | Changes in apps/backend/ or backend/ |
(api) | API endpoints, routes, controllers |
(auth) | Authentication, authorization |
(db) | Database schemas, models, migrations |
(ui) | UI components, styling |
(ci) | CI/CD pipelines, GitHub Actions |
(config) | Configuration files, environment setup |
| (omitted) | Changes span multiple modules or are global |
<type>(<scope>): <subject>
<body>
Closes #123If the uncommitted changes contain multiple unrelated changes, suggest splitting them into separate commits:
git add commands to stage each group separately:# Commit 1: Feature changes
git add src/api/vendors/
git commit -m "feat(api): add vendor rating endpoint"
# Commit 2: Doc updates
git add docs/
git commit -m "docs: update API reference for vendor rating"
Present the commit message(s) in a clean, copy-pasteable format:
feat(api): add vendor rating endpoint
Implement POST /api/v1/vendors/:id/rate to allow authenticated users
to submit ratings. Includes input validation and duplicate-vote guard.
Closes #123
If multiple commits are suggested, number them and provide the staging commands.
Always output:
git add commands for each logical groupChanges detected: Modified backend/src/routes/auth.ts to fix token expiration handling.
fix(auth): handle expired refresh token gracefully
Return 401 with a clear error message instead of crashing when
the refresh token has expired. The client can now detect this
and redirect to the login page.
Changes detected: Added new vendor endpoint + updated documentation + fixed lint config.
Commit 1/3:
git add backend/src/routes/vendors/
git commit -m "feat(api): add vendor assignment endpoint
Implement POST /api/v1/events/:id/vendors to assign vendors to events.
Includes RBAC check for organizer role.
Closes #45"
Commit 2/3:
git add docs/
git commit -m "docs: add vendor API reference"
Commit 3/3:
git add .eslintrc.js
git commit -m "chore(config): update eslint rules for new endpoint patterns"
docs/contributing/CONTRIBUTING.mddocs/guides/GIT_WORKFLOW.md