commit

Create commits with code quality checks and conventional commit messages

설치로 이동

저장소: diegosouzapw/awesome-omni-skill
최근 소스 활동: 2026년 3월 1일 18:11
감지된 SKILL.md 언어: 영어
스타: 50
포크: 19

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/diegosouzapw/awesome-omni-skill --skill commit

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

파일 탐색기

2 개 파일

SKILL.md

소스 지침 · 읽기 전용 미리보기

검색으로 돌아가기 설치로 돌아가기

name	commit
description	Create commits with code quality checks and conventional commit messages

/commit - Commit Creation Skill

Create commits with proper code quality checks and conventional commit messages.

Language Requirement

IMPORTANT: All commit messages MUST be written in English.

Step 0: Verify Branch (MANDATORY)

CRITICAL: This step MUST be performed before any other step.

Check Current Branch

git branch --show-current

Branch Validation Rules

Current Branch	Action
`main`	❌ STOP - Never commit directly to main
`develop`	❌ STOP - Never commit directly to develop
`feature/*`	✅ Proceed with commit
`bugfix/*`	✅ Proceed with commit
`hotfix/*`	✅ Proceed with commit
`docs/*`	✅ Proceed with commit
`refactor/*`	✅ Proceed with commit

If on `develop` or `main`

STOP immediately - Do not proceed with commit
Inform the user about the branch policy violation

Create a feature branch:

git fetch origin
git checkout -b feature/<issue-number>-<description> origin/develop

After branch creation, proceed with the commit workflow

Error Message Template

If on protected branch, display:

⚠️ ERROR: Cannot commit directly to '{branch_name}' branch.

This project uses Git Flow. Please create a feature branch first:
  git checkout -b feature/<issue>-<description> origin/develop

See .claude/instructions.md for branching guidelines.

Pre-flight Checks (MANDATORY)

1. Format Code

cargo fmt --all

This automatically formats all code. Stage any formatting changes.

2. Clippy Check

cargo clippy --all-targets --all-features -- -D warnings

CRITICAL: Zero warnings required. Fix all issues before committing.

3. Security Check

Verify no secrets in staged files:

Files to check: git diff --cached --name-only

If secrets are found:

Remove secrets from files
Add file to .gitignore if appropriate
WARN the user about the security issue

Steps

Step 1: Check Current Status

git status

Identify:

Staged changes
Unstaged changes
Untracked files

Step 2: Run Pre-flight Checks

Execute format and clippy checks. If clippy fails:

Fix all warnings
Re-run clippy until clean

Step 3: Stage Changes

# Stage specific files
git add <files>

# Or stage all changes
git add .

Step 4: Review Staged Changes

git diff --cached

Verify all intended changes are staged.

Step 5: Generate Commit Message

Use Conventional Commits format:

<type>(<scope>): <description>

[optional body]

[optional footer]
Co-Authored-By: Claude <noreply@anthropic.com>

Types

Type	Description
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only changes
`style`	Formatting, no code change
`refactor`	Code change that neither fixes a bug nor adds a feature
`perf`	Performance improvement
`test`	Adding or correcting tests
`chore`	Maintenance tasks
`ci`	CI configuration changes

Scope (Optional)

Common scopes for this project:

domain - Domain layer changes
application - Application layer changes
adapters - Adapter layer changes
ports - Port definitions
cli - CLI changes
deps - Dependency updates

Examples

feat(cli): add --verbose flag for detailed output

fix(domain): correct dependency graph cycle detection

docs: update README with new installation instructions

refactor(adapters): extract common HTTP client logic

test(application): add unit tests for GenerateSbomUseCase

Step 6: Create Commit

Use HEREDOC for proper formatting:

git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>

<body if needed>

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

Step 7: Verify Commit

git log -1 --format=full

Confirm:

Commit message is in English
Type is correct
Co-Authored-By is present
No secrets in the commit

Error Handling

Clippy Failures

If clippy fails with warnings:

Read the warning messages carefully
Fix each warning
Re-run clippy
Once clean, proceed with commit

Pre-commit Hook Failures

If a pre-commit hook rejects the commit:

Read the hook output
Fix the issues
Stage the fixes
Create a NEW commit (do not amend unless specifically needed)

Secrets Detected

If secrets are found in staged files:

STOP - Do not commit
Remove secrets from the file
Consider if the file should be in .gitignore
WARN the user
Ask for confirmation before proceeding

Example Usage

User: "変更をコミットして"

Claude executes /commit skill:

Runs cargo fmt --all
Runs cargo clippy --all-targets --all-features -- -D warnings
Checks for secrets in staged files
Reviews changes with git diff --cached
Generates conventional commit message in English
Creates commit with Co-Authored-By trailer
Confirms commit with git log -1
Reports success to user

commit

소스 정보

설치 방법

소스 파일 검토

이 저장소의 다른 Skills

이 저장소의 다른 Skills

/commit - Commit Creation Skill

Language Requirement

Step 0: Verify Branch (MANDATORY)

Check Current Branch

Branch Validation Rules

If on develop or main

Error Message Template

Pre-flight Checks (MANDATORY)

1. Format Code

2. Clippy Check

3. Security Check

Steps

Step 1: Check Current Status

Step 2: Run Pre-flight Checks

Step 3: Stage Changes

Step 4: Review Staged Changes

Step 5: Generate Commit Message

Types

Scope (Optional)

Examples

Step 6: Create Commit

Step 7: Verify Commit

Error Handling

Clippy Failures

Pre-commit Hook Failures

Secrets Detected

Example Usage

/commit - Commit Creation Skill

Language Requirement

Step 0: Verify Branch (MANDATORY)

Check Current Branch

Branch Validation Rules

If on develop or main

Error Message Template

Pre-flight Checks (MANDATORY)

1. Format Code

2. Clippy Check

3. Security Check

Steps

Step 1: Check Current Status

Step 2: Run Pre-flight Checks

Step 3: Stage Changes

Step 4: Review Staged Changes

Step 5: Generate Commit Message

Types

Scope (Optional)

Examples

Step 6: Create Commit

Step 7: Verify Commit

Error Handling

Clippy Failures

Pre-commit Hook Failures

Secrets Detected

Example Usage

If on `develop` or `main`

If on `develop` or `main`