apw-commitlisted
Install: claude install-skill AgenticPW/AgenticPW
Use this skill when the user wants to commit (and optionally push) pending changes. Follow every step below in order.
## Output style
When this skill asks for a plan, report, summary, status update, or other chat-facing output, prefer bullet points or numbered lists over plain paragraphs. Keep each item concise and content-bearing. Omit language that only smooths tone, repeats context, or adds "language sugar" without changing the meaning.
## Step 1 — Inspect pending changes
Run the following commands to understand what will be committed:
```bash
git status
git diff HEAD
```
If there are no changes (clean working tree and staging area), tell the user there is nothing to commit and stop.
## Step 2 — Check for a commit schema
Look for the file `.claude/skills/apw-commit/COMMIT_SCHEMA.md` in the repository root.
**If it exists:** read it and use it as the authoritative format guide for all commit messages in this project. Proceed to Step 3.
**If it does not exist:**
1. Present the following suggested default schema to the user:
---
**Suggested commit message schema:**
```
<type>(<scope>): <short summary>
<body — what changed and why, optional>
<footer — breaking changes, issue refs, co-authors, optional>
```
Types: `feat`, `fix`, `refactor`, `chore`, `docs`, `test`, `style`, `perf`
Rules:
- Subject line ≤ 72 characters
- Use imperative mood ("add", not "added")
- Body wraps at 80 characters
- Reference issues as `Closes #123`
---
2. Ask the user: **"Use this sc