repositories / dotfiles

dotfiles

bugabingas dorkfiles

owned by bugabinga

opencode/commands/commit.md

Raw

description: Prepare a commit for current changes agent: historian

Load the /git-commit skill.

Gather context

Current branch: !git branch --show-current

Staged files: !git diff --cached --name-only

Unstaged changes: !git diff --name-only

Recent commits: !git log --oneline -5

Last commit: !git log -1 --stat

Staged diff (to be committed)

!git diff --cached

Unstaged diff (won't be committed)

!git diff

Staging guidance

If unstaged files need to be committed, ask the user:

Do NOT run git add yourself — wait for the user to confirm which files to stage.

Once staged, re-run the staged diff section and proceed with the commit plan.

Plan (only after staging is confirmed)

Given the staged changes above:

  1. Classify the change type (feat/fix/docs/style/refactor/test/chore)
  2. Determine the scope (affected subsystem or module)
  3. Write a concise, imperative subject line (≤72 chars, no trailing period)
  4. Add a body explaining what and why (not how), wrapped at 72 cols
  5. Add a footer for breaking changes or issue refs if relevant
  6. Check it follows conventional commit format
Markdown source
---
description: Prepare a commit for current changes
agent: historian
---

Load the /git-commit skill.

## Gather context

Current branch:
!`git branch --show-current`

Staged files:
!`git diff --cached --name-only`

Unstaged changes:
!`git diff --name-only`

Recent commits:
!`git log --oneline -5`

Last commit:
!`git log -1 --stat`

## Staged diff (to be committed)

!`git diff --cached`

## Unstaged diff (won't be committed)

!`git diff`

## Staging guidance

If unstaged files need to be committed, ask the user:

- Which files should be staged? (e.g., "stage src/ and tests/, but not docs/")
- Or offer to stage all: `git add -A`

Do NOT run `git add` yourself — wait for the user to confirm which files to stage.

Once staged, re-run the staged diff section and proceed with the commit plan.

## Plan (only after staging is confirmed)

Given the staged changes above:

1. Classify the change type (feat/fix/docs/style/refactor/test/chore)
2. Determine the scope (affected subsystem or module)
3. Write a concise, imperative subject line (≤72 chars, no trailing period)
4. Add a body explaining _what_ and _why_ (not _how_), wrapped at 72 cols
5. Add a footer for breaking changes or issue refs if relevant
6. Check it follows conventional commit format