/commit

> Stage changes, generate a meaningful commit message, and commit.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/commit is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Stage changes, generate a meaningful commit message, and commit.

Teams using /commit should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/commit/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/development/commit/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/commit/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /commit Compares

Feature / Agent	/commit	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Stage changes, generate a meaningful commit message, and commit.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /commit

> Stage changes, generate a meaningful commit message, and commit.

## Usage
```
/commit [--all] [--amend] [-m "message"]
```

## What It Does
Analyzes staged and unstaged changes, generates a commit message that summarizes the "why" not just the "what", and creates the commit. Follows conventional commit format when the project uses it.

## Implementation
1. **Analyze changes** -- run `git diff --staged` and `git status`.
2. **Classify changes** -- feature, fix, refactor, docs, test, chore.
3. **Generate message** -- summarize the intent of changes in 1-2 sentences. Use conventional commit prefix if project convention detected.
4. **Stage** (if `--all`) -- add all modified tracked files.
5. **Commit** -- create the commit with the generated or provided message.
6. **Verify** -- run `git status` to confirm clean state.

## Examples
```bash
# Commit staged changes with auto-generated message
/commit

# Stage all changes and commit
/commit --all

# Commit with explicit message
/commit -m "fix: resolve race condition in session handler"

# Amend the last commit
/commit --amend
```

## Command