commitlisted
Install: claude install-skill real-case/marvin-toolkit
Analyze staged git changes and generate a conventional commit message. Follow the full workflow below.
## Workflow
### 1. Check State
Run in parallel:
```bash
git status
git diff --stat
git diff --cached --stat
git log --oneline -10
git diff
git diff --cached
```
If no changes exist (nothing staged, unstaged, or untracked) — inform the user and stop.
### 2. Stage Changes
Prefer staging specific files by name over `git add -A` or `git add .`.
After staging, detect sensitive files:
```bash
git diff --cached --name-only | grep -iE '\.(env|pem|key|p12|pfx)$|credentials|secret|token|id_rsa|id_ed25519|npmrc|pypirc'
```
If matches found:
1. Unstage them: `git reset HEAD <file>`
2. Warn the user
3. Do not proceed until resolved
Confirm staged content with `git diff --cached --stat` before continuing.
### 3. Generate Message
If a message was provided via `$ARGUMENTS`, use it directly — skip to step 4.
Otherwise, analyze the staged diff and generate a message per the format below.
**Commit message format:**
```
<type>(<scope>): <subject>
<body>
<footer>
```
- **Type:** `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `ci`, `perf`, `style`, `build`
- **Scope:** most affected module or directory (optional but preferred)
- **Subject:** imperative mood, max 72 chars, no period at end
- **Body:** 1–2 sentences explaining **why**, not what. Omit for trivial changes.
- **Footer:** `BREAKING CHANGE: <description>` if applicable
Match the existing commit style from `git l