What is update-branch-name?

A command procedure for renaming the current Git branch, a separate line of development in a code repository.

Use it to compare the branch with main, inspect the changed files, choose a suitable name, rename the branch, and confirm the result.

It helps choose a descriptive name based on the actual changes and verifies that the rename succeeded.

How giselles-ai/giselle configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to giselles-ai/giselle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/giselles-ai/giselle/main/.claude/commands/update-branch-name.md

Clone the repo

git clone --depth 1 https://github.com/giselles-ai/giselle

Made for: Claude Code.

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/giselles-ai/giselle/update-branch-name/github.svg)](https://agentmods.dev/commands/giselles-ai/giselle/update-branch-name)

Your own site

<a href="https://agentmods.dev/commands/giselles-ai/giselle/update-branch-name"><img src="https://agentmods.dev/badge/commands/giselles-ai/giselle/update-branch-name/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/giselles-ai/giselle/update-branch-name"><img src="https://agentmods.dev/badge/commands/giselles-ai/giselle/update-branch-name.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 94 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.00000	$0.00094
Opus 5.5	$0.00000	$0.00038
Sonnet 5.5	$0.00000	$0.00019
Haiku 4.5	$0.00000	$0.00009

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

Security

Grade A, and why

update-branch-name 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 2mo 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

update-branch-name — 100% identical, 0 lines differ
update-branch-name — 100% identical, 0 lines differ

.claude/commands/update-branch-name.md · 10 lines

What it actually says

Update Branch Name

Follow these steps to update the current branch name:

Check differences between current branch and main branch HEAD using git diff main...HEAD
Analyze the changed files to understand what work is being done
Determine an appropriate descriptive branch name based on the changes
Update the current branch name using git branch -m [new-branch-name]
Verify the branch name was updated with git branch

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.

2mo ago First seen · 10 lines · 0 tokens per session scan A dade40f7da94

Subscribe to this mod's changes

update-branch-name is a command published in the GitHub repository giselles-ai/giselle (559 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 94 tokens. 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-30.

Git and workflow agent ai ai-agent genai generative-ai nextjs

update-branch-name next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
update-branch-namegiselles-ai/giselle	Command	559	3d ago	Apache-2.0	A	0	Claude Code
CHANGELOGbytedance/UI-TARS-desktop	Command	40k	29d ago	Apache-2.0	A	0	Claude Code
implement-featureHoangNguyen0403/agent-skills-standard	Command	583	today	MIT	A	0	Claude Code
diff-scriptmendixlabs/mxcli	Command	137	yesterday	Apache-2.0	A	10	Claude Code
dashboard-session-diffBlackBeltTechnology/pi-agent-dashboard	Command	341	2d ago	MIT	A	31	Claude Code
commitechoVic/blade-code	Command	181	24d ago	MIT	A	8	Claude Code
review.v1stakpak/agent	Command	1.9k	4mo ago	Apache-2.0	A	13	Claude Code

giselle: Command for Claude Code