메뉴
Conventional commit format and workflow with Jira ticket integration
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/alexandrebenkendorf/agents-playbooks --skill git-commit-conventions명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Code standards and conventions for React, TypeScript, and domain-driven front-end architecture
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Best practices for structuring React components - function declarations, file organization, and Single Responsibility Principle
SKILL.md 표시 중
SOC 직업 분류 기준
| name | Git Commit Conventions |
| description | Conventional commit format and workflow with Jira ticket integration |
Guidelines for creating properly formatted commit messages with Jira ticket numbers.
Set your Jira project prefix in README.md:
# Project Configuration
- **Jira Ticket Prefix**: `PROJ` (e.g., JIRA, DEV, TASK)
- **Branch Format**: `<PREFIX>-<number>-description`
<type>: <PREFIX>-<ticket-number> <description>
Where:
<type> = Commit type (feat, fix, docs, etc.)<PREFIX> = Your Jira project prefix (PROJ, JIRA, etc.)<ticket-number> = Jira ticket number<description> = Imperative descriptionIf there is no ticket in the branch name and recent commits do not include tickets, omit the ticket and use:
<type>: <description>
| Type | Usage |
|---|---|
feat | A new feature |
fix | A bug fix |
docs |
| Documentation only changes |
style | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) |
refactor | A code change that neither fixes a bug nor adds a feature |
perf | A code change that improves performance |
test | Adding missing tests or correcting existing tests |
build | Changes that affect the build system or external dependencies |
ci | Changes to our CI configuration files and scripts |
chore | Other changes that don't modify src or test files |
revert | Reverts a previous commit |
rollback | Rolling back to a previous version |
PROJ-134713-FE-Add-GitHub-unittest.instructions.md-for-vitest → PROJ-134713TASK-456-implement-user-auth → TASK-456<type>: <description>.# Adding a new feature
git commit -m "feat: PROJ-134713 Add GitHub unittest instructions for Vitest best practices"
git commit -m "feat: TASK-456 Implement user authentication flow"
# Fixing a bug
git commit -m "fix: PROJ-134714 Resolve memory leak in component unmounting"
git commit -m "fix: JIRA-789 Correct email validation regex"
# Documentation update
git commit -m "docs: PROJ-134715 Update API documentation for user service"
# Refactoring code
git commit -m "refactor: PROJ-134716 Simplify user authentication logic"
# Rolling back changes
git commit -m "rollback: PROJ-134717 Revert to previous version due to performance issues"
# Adding tests
git commit -m "test: PROJ-134718 Add unit tests for UserProfile component"
# Performance improvement
git commit -m "perf: PROJ-134719 Optimize database query for user search"
When user says "commit the changes" or similar:
git status to see modified filesgit diff --staged (or git diff if nothing staged) to review actual code changes
git reset HEAD <file>featfixtestdocsrefactorperfbuild or ciREADME.md if availablePROJ-, TASK-, etc.)Each commit should represent ONE logical change:
✅ Good - Focused commits:
# Commit 1
git add src/components/UserProfile.tsx
git commit -m "feat: PROJ-12345 Add user avatar display to UserProfile"
# Commit 2
git add src/utils/validation.ts
git commit -m "fix: PROJ-12345 Correct email validation regex"
# Commit 3
git add README.md
git commit -m "docs: PROJ-12345 Update UserProfile component documentation"
❌ Bad - Mixed changes:
# Mixing feature, fix, and docs in one commit
git add src/components/UserProfile.tsx src/utils/validation.ts README.md
git commit -m "feat: PROJ-12345 Add avatar, fix validation, update docs"
When to split commits:
git status outputBest (let AI analyze):
"Commit the changes"
"Review my staged changes and create a commit message"
Good (with context):
"I've updated the authentication flow and added error handling.
Check my changes and create a commit message."
Acceptable (manual description):
"Create a commit message. I added unit tests for the UserProfile component
and fixed a bug in the validation logic."
git add .git status to see what files changedgit diff --staged to see the actual code changesfeat: PROJ-134801 Add error handling to authentication flow
git commit -m "feat: PROJ-134801 Add error handling to authentication flow"