git-commit

Files (1)

• SKILL.md

SKILL.md (first lines)

## Critical Rules

- ALWAYS use conventional-commits format: `type(scope): description`
- ALWAYS keep the first line under 72 characters
- ALWAYS ask for user confirmation before committing
- NEVER be overly specific (avoid counts like "6 subsections", "3 files")
- NEVER include implementation details in the title
- NEVER use `-n` flag unless user explicitly requests it
- NEVER use `git push --force` or `git push -f` (destructive, rewrites history)
- NEVER proactively offer to commit - wait for user to explicitly request it

---

## Commit Format

```
type(scope): concise description

- Key change 1
- Key change 2
- Key change 3
```

### Types

| Type | Use When |
|------|----------|
| `feat` | New feature or functionality |
| `fix` | Bug fix |
| `docs` | Documentation only |
| `chore` | Maintenance, dependencies, configs |
| `refactor` | Code change without feature/fix |
| `test` | Adding or updating tests |
| `perf` | Performance improvement |
| `style` | Formatting, no code change |

### Scopes

| Scope | When |
|-------|------|
| `logic` | Changes in `skills/cebojon-logic/` |
| `script` | Changes in `clasificador_municipios.py` |
| `skills` | Changes in other `skills/` |
| `docs` | Changes in `docs/` |
| `config` | Changes in `requirements.txt`, `.venv`, etc. |
| *omit* | Multiple scopes or root-level |

---

## Workflow

1. **Analyze changes**
2. **Draft commit message**
3. **Present to user for confirmation**
4. **Execute commit**

From Juliotamara23/GeoPulse, Apache-2.0.

More from Juliotamara23/GeoPulse