/refactor

description: Refactor commit. Use for refactoring, restructure, reorganize, clean up code.
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

Refactor Commit

Current State

!`git status`

Changes

!`git diff --stat`

Instructions

Create a refactoring commit (no behavior change).

1. Stage all changes: `git add -A` 2. Analyze modified files to determine scope 3. Generate commit message:

• If `$ARGUMENTS` provided: `refactor(scope): $ARGUMENTS`
• If empty: analyze diff and describe restructure

4. Format: `refactor(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 Step 7/8, not by this quick command)

Note: Refactor = code restructure WITHOUT functional changes.