Menü
Create commits with code quality checks and conventional commit messages
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Orchestrate complete issue implementation workflow from branch to PR
Create Pull Requests with pre-flight checks and proper formatting
Decompose a large GitHub Issue (epic, refactor, or feature) into subtask Issues, each small enough for a single focused PR
Standardized release workflow with version updates and CHANGELOG management
Spawn a Reviewer Agent to evaluate code changes against architecture, design, and quality criteria
Run all validations before pushing to remote
| name | commit |
| description | Create commits with code quality checks and conventional commit messages |
Create commits with proper code quality checks and conventional commit messages.
IMPORTANT: All commit messages MUST be written in English.
CRITICAL: This step MUST be performed before any other step.
git branch --show-current
| 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 |
develop or maingit fetch origin
git checkout -b feature/<issue-number>-<description> origin/develop
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.
Note:
cargo fmtis handled automatically by the.githooks/pre-commithook.cargo clippyandcargo testare handled by the.githooks/pre-pushhook at push time. Runmake setuponce to activate these hooks if you haven't already.
Verify no secrets in staged files:
.env files with real valuescredentials.json or similarFiles to check: git diff --cached --name-only
If secrets are found:
.gitignore if appropriategit status
Identify:
Run the security check. If secrets are found, stop immediately.
# Stage specific files
git add <files>
# Or stage all changes
git add .
git diff --cached
Verify all intended changes are staged.
Use Conventional Commits format:
<type>(<scope>): <description>
[optional body]
[optional footer]
Co-Authored-By: Claude <noreply@anthropic.com>
| 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 |
Common scopes for this project:
domain - Domain layer changesapplication - Application layer changesadapters - Adapter layer changesports - Port definitionscli - CLI changesdeps - Dependency updatesfeat(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
Use HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>
<body if needed>
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"
git log -1 --format=full
Confirm:
If clippy fails with warnings:
If a pre-commit hook rejects the commit:
If secrets are found in staged files:
.gitignoreUser: "変更をコミットして"
Claude executes /commit skill:
cargo fmt --allcargo clippy --all-targets --all-features -- -D warningsgit diff --cachedgit log -1