prowler-cloud/prowler/prowler-commit

type(scope): concise description
 
- Key change 1
- Key change 2
- Key change 3

# GOOD - Concise and clear
feat(api): add provider connection retry logic
fix(ui): resolve dashboard loading state
chore(skills): add Celery documentation
docs: update installation guide
 
# BAD - Too specific or verbose
feat(api): add provider connection retry logic with exponential backoff and jitter (3 retries max)
chore(skills): add comprehensive Celery documentation covering 8 topics
fix(ui): fix the bug in dashboard component on line 45

# GOOD - High-level changes
- Add retry mechanism for failed connections
- Document task composition patterns
- Expand configuration reference
 
# BAD - Too detailed
- Add retry with max_retries=3, backoff=True, jitter=True
- Add 6 subsections covering chain, group, chord
- Update lines 45-67 in dashboard.tsx

Single file changed?
├─ Yes → May omit body, title only
└─ No → Include body with key changes
 
Multiple scopes affected?
├─ Yes → Omit scope: `feat: description`
└─ No → Include scope: `feat(api): description`
 
Fixing a bug?
├─ User-facing → fix(scope): description
└─ Internal/dev → chore(scope): fix description
 
Adding documentation?
├─ Code docs (docstrings) → Part of feat/fix
└─ Standalone docs → docs: or docs(scope):

# Check current state
git status
git diff --stat HEAD
 
# Standard commit
git add <files>
git commit -m "type(scope): description"
 
# Multi-line commit
git commit -m "$(cat <<'EOF'
type(scope): description
 
- Change 1
- Change 2
EOF
)"
 
# Amend last commit (same message)
git commit --amend --no-edit
 
# Amend with new message
git commit --amend -m "new message"