Commit

Create well-structured git commits with meaningful messages.

Usage

/commit [type]

Arguments:

• type - Optional: feat, fix, refactor, docs, test, chore

Commit Process

Step 1: Analyze Changes

Run these commands to understand what changed:

git status
git diff --staged
git diff

If nothing is staged, ask whether to stage all changes or specific files.

Step 2: Categorize Changes

Determine the primary change type:

Type	When to Use
feat	New feature or capability
fix	Bug fix or correction
refactor	Code restructuring (no behavior change)
docs	Documentation only
test	Adding or updating tests
chore	Build, tooling, dependencies

Step 3: Craft the Message

Follow this format:

<type>: <concise summary in imperative mood>

<optional body explaining what and why>

<optional footer with references>

Rules:

• Summary line: 50 chars or less, imperative mood ("Add" not "Added")
• Body: Wrap at 72 chars, explain motivation and context
• Footer: Issue references, breaking changes

Good Examples:

feat: add user authentication with JWT tokens

Implement login/logout flow with secure token storage.
Tokens expire after 24 hours and refresh automatically.

Closes #123

fix: prevent crash when network unavailable

Handle nil response gracefully instead of force unwrapping.

Bad Examples:

fixed stuff          # Too vague
WIP                  # Not descriptive
Updated files        # Says nothing useful

Step 4: Execute

Stage files if needed and create the commit:

git add <files>
git commit -m "<message>"

Show the result with git log -1.

Guidelines

• One logical change per commit
• Don't mix unrelated changes
• Never commit secrets or credentials
• Reference issues when applicable
• Keep commits atomic and revertable