A command for creating a Git commit containing documentation changes. It limits staging to Markdown, text, reStructuredText, and comment or JSDoc edits, then uses a “docs” commit type.

Use it to commit README files, other documentation, comments, or JSDoc updates and apply the related changelog and patch-version update.

It prevents unrelated source changes from being mixed into a documentation commit. It also keeps documentation history and commit messages consistent.

docs — Command for coding agents by fusengine: A command for creating a Git commit containing documentation…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/fusengine/agents/docs

Clone the repo

git clone --depth 1 https://github.com/fusengine/agents

Or install fuse-commit-pro, the plugin that ships this one along with the rest of its 4 skills, 10 commands, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/fusengine/agents/docs.svg)](https://agentmods.dev/commands/fusengine/agents/docs)

Your own site

<a href="https://agentmods.dev/commands/fusengine/agents/docs"><img src="https://agentmods.dev/badge/commands/fusengine/agents/docs.svg" alt="Measured on agentmods" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 325 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00018	$0.00325
Opus 5	$0.00009	$0.00162
Sonnet 5	$0.00004	$0.00065
Haiku 4.5	$0.00002	$0.00032

Measured yesterday against content hash 3f33ac15e659, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/commit-pro/commands/docs.md · 35 lines

What it actually says

Documentation Commit

Current State

!git status

Documentation Files Changed

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

Instructions

Create a documentation commit.

Stage only documentation files:
- *.md files
- *.txt, *.rst files
- Files with only comment/JSDoc changes
Analyze files to determine scope
Generate commit message:
- If $ARGUMENTS provided: docs(scope): $ARGUMENTS
- If empty: generate from file names
Format: docs(scope): imperative description
NO AI SIGNATURE: Never add Co-authored-by, Generated by, or any AI mention
Ask confirmation before committing
Execute and show result
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)

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 35 lines · 18 tokens per session scan A 3f33ac15e659

Subscribe to this mod's changes

docs is a command published in the GitHub repository fusengine/agents (25 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 325 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Commits Git and workflow Writing and docs claude-agent claude-agents claude-code claude-code-plugin claude-skills claudecode

commit-claude-config

Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).

solanabr/solana-ai-kit · 35 tokens

commit

Analyze git diffs or staged changes and generate conventional commit messages that explain WHY a change was made. Supports auto-detecting type and scope, intelligent file staging, and interactive overrides. Use when asked to "write a commit message", "generate a commit", "describe my changes", "commit this"…

nitinjain999/platform-skills · 74 tokens

docs