/docs

description: Documentation commit. Use for update docs, documentation, readme, jsdoc, comments.
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

Documentation Commit

Current State

!`git status`

Documentation Files Changed

!`git diff --stat -- '*.md' '*.txt' '*.rst'`

Instructions

Create a documentation commit.

1. Stage only documentation files:

• `*.md` files
• `*.txt`, `*.rst` files
• Files with only comment/JSDoc changes

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

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

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