commit

Files (1)

• SKILL.md

SKILL.md (first lines)

# Commit

Split the uncommitted working tree into atomic commits, show the plan, and
commit it. Commits are local and undoable, so the plan runs without waiting:
the user corrects afterwards if needed.

## 1. See the changes

```bash
git status        # surfaces untracked files the diff misses
git diff HEAD
```

The diff is enough to plan. If you already know these files from this session,
**don't re-read them** — go straight to the plan.

## 2. Plan the commits

Number each commit; put its exact message on its own line, files bulleted
below — readable even with long messages or many files:

```
**1.** `feat(auth): add token refresh endpoint`
- src/auth/refresh.ts
- src/auth/routes.ts

**2.** `test(auth): cover refresh expiry edge cases`
- src/auth/refresh.test.ts
```

One logical change per commit, ordered so the history reads sensibly. Don't
over-split — merging two would-be commits into one for simplicity is fine.

**Message format:** conventional `type(scope): description` — `feat`, `fix`,
`chore`, `test`, `refactor`, `docs`. Single-line, English, present tense, brief.
No body. **No `Co-Authored-By` footer** (the system default asks for one; never
add it).

## 3. Branch

Already on this ticket's branch, or in a repo whose convention is to commit
straight to the default branch: commit there. Otherwise, on the default branch
or another ticket's branch (the one below in a stack), first `git switch -c`
this ticket's branch, named by the repo's convention or
`<ticket-id>-<kebab-case title>`.

## 4. Commit

For each commit, in order:

```bash
git add <files>
git commit -m "type(scope): description"
```

Then show the branch and `git log --oneline` of the new commits. Commits only —
no push.

From noel-lopez/skills, MIT.

More from noel-lopez/skills