Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub ghozimahdi/gm-claude-plugins --plugin ufilHow this command is triggered — by the user, by Claude, or both
Slash command
/ufil:commit [message or leave empty for auto-detect]haikuThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Create a git commit using **Conventional Commits** format with ticket ID. Arguments: $ARGUMENTS (optional commit message or scope hint) ## Commit Format ### Types | Type | When to use | | ------------ | -------------------------------------------------------- | | `feat` | New feature or capability | | `fix` | Bug fix | | `refactor` | Code restructure without behavior change | | `chore` | Maintenance (deps update, confi...
/commitStages unstaged changes based on git status and diff analysis, then creates a commit with a generated message. Uses current branch and recent commit history for context.
/commitStages changes and commits locally using Conventional Commits format. Analyzes git status/diffs, drafts typed message with scope, confirms with user before git add and commit.
/commitCreates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.
/commitCreates well-formatted git commits with conventional messages and emojis. Runs pre-commit checks (lint/format/build/docs), auto-stages files if needed, analyzes diffs, and suggests splitting multi-change commits unless --no-verify.
/commitRuns pre-commit git checks, quality gates (lint, typecheck, tests), code review for issues; drafts conventional commit message; stages specific files and commits. Supports --no-verify, --amend, --push options.
/commitAnalyzes current git diff, generates 3 conventional commit message options (concise, detailed, comprehensive), presents for user selection, and executes git commit.
Share bugs, ideas, or general feedback.
Create a git commit using Conventional Commits format with ticket ID.
Arguments: $ARGUMENTS (optional commit message or scope hint)
<type> (TICKET-ID): <description>
[optional body]
| Type | When to use |
|---|---|
feat | New feature or capability |
fix | Bug fix |
refactor | Code restructure without behavior change |
chore | Maintenance (deps update, config, CI, scripts) |
docs | Documentation only |
style | Formatting, whitespace, semicolons (no logic change) |
test | Adding or updating tests |
perf | Performance improvement |
ci | CI/CD pipeline changes |
build | Build system or external dependency changes |
revert | Revert a previous commit |
PROP-123)$ARGUMENTS contains a ticket ID, use itfeat (PROP-123): add tenant list page with pagination
fix (PROP-456): handle null amount in checkout DTO
refactor (PROP-789): extract token refresh into interceptor
chore (PROP-100): bump freezed to 3.0.0
test (PROP-404): add bloc tests for detail page
git status to see all changed/untracked filesgit diff --staged to see staged changesgit diff to see unstaged changesgit branch --show-current to get current branch name (may contain ticket ID).env, credentials, API keys)git add -A$ARGUMENTS provided:
features/ or new entity/bloc/page -> featfixrefactortestchoredocsPROP-123 -> ticket PROP-123)$ARGUMENTS is provided, use it as the description (still auto-detect type if not specified)<type> (TICKET-ID): <imperative verb> <what changed> (max 72 chars)
dart fix --apply lib/ before committing (if .dart files are staged)dart format lib test (if .dart files are staged)dart analyze lib test (if .dart files are staged)${CLAUDE_PLUGIN_ROOT}/docs/COMMIT_CONVENTION.md — Full commit message format and rules${CLAUDE_PLUGIN_ROOT}/docs/BRANCHING.md — Git branching strategy