/chore

description: Chore commit. Use for maintenance, deps, dependencies, config, cleanup, housekeeping.
argument-hint: "[description] | (empty for auto-detection)"
allowed-tools: Bash(git status:*), Bash(git diff:*), Bash(git add:*), Bash(git commit:*), Bash(git log:*), Bash(git tag:*), Bash(git push:*), Bash(git describe:*), Read, Edit
disable-model-invocation: false

Chore Commit

Current State

!`git status`

Changes

!`git diff --stat`

Instructions

Create a maintenance/chore commit.

1. Stage all changes: `git add -A` 2. Determine scope from files:

• `package.json` → `deps`
• Config files → `config`
• Linting → `lint`

3. Generate commit message:

• If `$ARGUMENTS` provided: `chore(scope): $ARGUMENTS`
• If empty: generate description

4. Format: `chore(scope): imperative description` 5. **NO AI SIGNATURE**: Never add Co-authored-by, Generated by, or any AI mention 6. Ask confirmation before committing 7. Execute and show result 8. Execute the `post-commit` skill (CHANGELOG + version bump only — no tag here; tagging is handled post-merge by `/fuse-commit-pro:commit`'s Steps 7–9 (merge, tag, release-workflow watch), not by this quick command — never call a release "published" from here)