What is trace-commit?

A command that writes a Conventional Commit message from the latest Codetape trace. Conventional Commits use labels such as feat, fix, or docs so changes are easier to understand.

Use it after a change to turn the newest trace log into a formatted commit message, optionally stage all files, and commit them.

It removes the need to reconstruct a commit summary from the work you just did. It also asks for confirmation before creating the Git commit.

trace-commit — Command for Claude Code by 888wing/codetape

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.

Clone the repo

git clone --depth 1 https://github.com/888wing/codetape

Made for: Claude Code.

Or install codetape, the plugin that ships this one along with the rest of its 2 skills, 7 commands.

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/888wing/codetape/trace-commit/github.svg)](https://agentmods.dev/commands/888wing/codetape/trace-commit)

Your own site

<a href="https://agentmods.dev/commands/888wing/codetape/trace-commit"><img src="https://agentmods.dev/badge/commands/888wing/codetape/trace-commit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/888wing/codetape/trace-commit"><img src="https://agentmods.dev/badge/commands/888wing/codetape/trace-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00010	$0.00237
Opus 5.5	$0.00004	$0.00095
Sonnet 5.5	$0.00002	$0.00047
Haiku 4.5	$0.00001	$0.00024

Measured 1mo ago against content hash 90453118e18b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

trace-commit 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 1mo ago.

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.

commands/trace-commit.md · 31 lines

What it actually says

Generate a well-structured commit message based on the most recent trace log.

Instructions

Find the most recent trace in .codetape/traces/ (by filename date)
Read the trace log
Generate a conventional commit message:
- Type: feat (new feature), fix (bug fix), refactor, docs, chore, perf, test
- Scope: primary component name from affected components
- Description: concise summary derived from trace summary
- Body: list key changes as bullet points
- Footer: note breaking changes if impact is High

Format:

{type}({scope}): {description}

- {change 1}
- {change 2}

BREAKING CHANGE: {if applicable}

Display the generated message
Ask: "Commit with this message? (y/n)"
If yes, run git add -A && git commit -m "{message}"

$ARGUMENTS

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.

1mo ago First seen · 31 lines · 10 tokens per session scan A 90453118e18b

Subscribe to this mod's changes

trace-commit is a command published in the GitHub repository 888wing/codetape (0 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 237 once invoked, about $0.0000 per session on Opus 5.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-08-31.

Claude Code Commits Git and workflow ai-coding changelog cursor developer-tools documentation

branch-commit

Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…

Mozurok/fhorja.dev · 111 tokens

approve-proposed

Atomically persist every file marked PROPOSED in the most recent prior assistant turn's ### Artifact changes block, promoting staged content to real files. Invoked on request only. Use when that block contained files marked PROPOSED and you have accepted the inline content of each. Do not use when the prior turn had…

Mozurok/fhorja.dev · 107 tokens

pr-package

Prepare a GitHub PR delivery package (branch, commits, PR title and body, reviewer notes) from the real git diff against an explicit base branch, persisted as PRPACKAGE.md, never inventing work outside the diff. Use when scope is done and diff is stable. Do not use mid-implementation, for a branch name (use…

Mozurok/fhorja.dev · 109 tokens

trace-commit