/test

description: Test commit. Use for add tests, update tests, test coverage, unit test, spec.
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

Test Commit

Current State

!`git status`

Test Files Changed

!`git diff --stat -- '*.test.*' '*.spec.*' '__tests__/*' 'test/*' 'tests/*'`

Instructions

Create a test commit.

1. Stage test files:

• `*.test.*`, `*.spec.*`
• `__tests__/*`, `test/*`, `tests/*`

2. Analyze test files to determine scope 3. Generate commit message:

• If `$ARGUMENTS` provided: `test(scope): $ARGUMENTS`
• If empty: generate from test names

4. Format: `test(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)