2.0 KiB
2.0 KiB
description, agent, model
| description | agent | model |
|---|---|---|
| Create git commit with auto-generated conventional commit message | build | opencode/deepseek-v4-flash-free |
Git Commit Command
Create a well-structured git commit by analyzing staged changes and generating a conventional commit message.
Phase 1: Gather Context
Run these commands in parallel to understand the current state:
git status- See all staged and unstaged changesgit diff --cached- View the actual staged changes that will be committedgit log --oneline -5- Review recent commit message style for consistency
Phase 2: Analyze Changes
Based on the staged diff, determine:
-
Change Type (use conventional commits):
feat: New featurefix: Bug fixrefactor: Code restructuring without behavior changedocs: Documentation onlytest: Adding or updating testschore: Maintenance tasksstyle: Formatting, whitespaceperf: Performance improvementci: CI/CD changes
-
Scope (optional): Affected module or component
-
Description: Concise summary focusing on WHY, not WHAT
Phase 3: Generate Commit Message
Format: type(scope): description
Rules:
- Use imperative mood ("Add feature" not "Added feature")
- Keep first line under 72 characters
- Focus on the purpose and impact
- Add body for complex changes explaining reasoning
Phase 4: Execute Commit
- If there are unstaged changes that should be included, ask user first
- Stage any additional files if requested
- Execute the commit with the generated message
- Run
git statusto verify success
Output Format
Commit Analysis
---------------
Type: [type]
Scope: [scope or "none"]
Files: [number] files changed
Generated Message:
[commit message]
Commit Status: [success/failure]
Safety Checks
- NEVER commit files that appear to contain secrets (.env, credentials, API keys)
- WARN if committing lock files or large binary files
- CONFIRM before committing if there are untracked files that might be forgotten