name	commit
description	Review staged changes and create a conventional git commit
when_to_use	When you want to commit staged changes following project conventions
argument-hint	optional: context or commit message hint
context	fork
allowed-tools	["bash","git_status","git_diff","git_add","git_commit"]

Review the currently staged changes and create a well-formed conventional commit.

Steps:

Run git status and git diff --cached to understand what is staged.
Write a concise commit message following the Conventional Commits format: <type>(<scope>): <description> where type is one of: feat, fix, docs, style, refactor, test, chore.
Keep the subject line under 72 characters.
Run git commit -m "<message>".

$ARGUMENTS

Más de este repositorio

mismo repositorio

Research and plan a large-scale mechanical change, then execute it in parallel across independent work units

Diagnose agent session issues — show recent logs, tool errors, and configuration problems

Review auto-memory entries and promote useful ones to CLAUDE.md or project memory files

Review changed code for reuse, quality, and efficiency, then fix any issues found

Capture the current session's repeatable process into a reusable SKILL.md file

Diagnose a frozen, slow, or stuck agent session by inspecting running processes and recent logs

name	commit
description	Review staged changes and create a conventional git commit
when_to_use	When you want to commit staged changes following project conventions
argument-hint	optional: context or commit message hint
context	fork
allowed-tools	["bash","git_status","git_diff","git_add","git_commit"]

Review the currently staged changes and create a well-formed conventional commit.

Steps:

Run git status and git diff --cached to understand what is staged.
Write a concise commit message following the Conventional Commits format: <type>(<scope>): <description> where type is one of: feat, fix, docs, style, refactor, test, chore.
Keep the subject line under 72 characters.
Run git commit -m "<message>".

$ARGUMENTS