What is git-worktree-runner completions.instructions.md?

Instructions for maintaining shell tab completion for the Git GTR command, across Bash, Zsh, and Fish.

Use them when adding or renaming Git GTR commands, flags, branches, editors, or AI adapters, and when testing the completion files.

They help keep command, option, branch, editor, and AI-tool suggestions accurate when the CLI changes.

How coderabbitai/git-worktree-runner configures GitHub Copilot

About the project

gtr is a command-line tool that manages Git worktrees, which let developers keep multiple branches checked out in separate directories at the same time. It automates worktree creation, branch setup, configuration copying, dependency installation, and workspace preparation for reviews, coding agents, and parallel development. The catalogue contains instructions for using gtr.

coderabbitai/git-worktree-runner · 1,808 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to coderabbitai/git-worktree-runner. 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/coderabbitai/git-worktree-runner/main/.github/instructions/completions.instructions.md

Clone the repo

git clone --depth 1 https://github.com/coderabbitai/git-worktree-runner

Made for: GitHub Copilot.

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/instructions/coderabbitai/git-worktree-runner/completions/github.svg)](https://agentmods.dev/instructions/coderabbitai/git-worktree-runner/completions)

Your own site

<a href="https://agentmods.dev/instructions/coderabbitai/git-worktree-runner/completions"><img src="https://agentmods.dev/badge/instructions/coderabbitai/git-worktree-runner/completions/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/instructions/coderabbitai/git-worktree-runner/completions"><img src="https://agentmods.dev/badge/instructions/coderabbitai/git-worktree-runner/completions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 781 This file is loaded in full into every session.

When invoked 781 The same file — it is already loaded in full.

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.00781	$0.00781
Opus 5.5	$0.00312	$0.00312
Sonnet 5.5	$0.00156	$0.00156
Haiku 4.5	$0.00078	$0.00078

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

Security

Grade A, and why

git-worktree-runner completions.instructions.md 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.

.github/instructions/completions.instructions.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Completions Instructions

Generated Files

completions/gtr.bash (Bash), completions/_git-gtr (Zsh), and completions/git-gtr.fish (Fish) are generated by scripts/generate-completions.sh. Each file starts with an AUTO-GENERATED ... DO NOT EDIT MANUALLY header. CI (.github/workflows/lint.yml) runs ./scripts/generate-completions.sh --check and fails when any committed file differs from the generator output.

Sources of truth:

Adapter names: _EDITOR_REGISTRY and _AI_REGISTRY in lib/adapters.sh, plus any adapters/{editor,ai}/*.sh file overrides.
Config keys: _CFG_KEY_MAP in lib/config.sh.
Commands, their flags, and which commands accept branch arguments: the generate_bash, generate_zsh, and generate_fish templates inside the script.

git gtr completion <shell> (lib/commands/completion.sh) resolves the asset from the source checkout or the Homebrew install layout. For bash and fish it prints the generated file; for zsh it prints a zstyle + fpath + compinit snippet that puts the generated _git-gtr on your fpath. It never builds completions at runtime.

Making Changes

Change	Edit	Then
New editor or AI adapter	registry line in `lib/adapters.sh`	`./scripts/generate-completions.sh`
New config key	`_CFG_KEY_MAP` in `lib/config.sh`	`./scripts/generate-completions.sh`
New command or flag	all three `generate_*` templates in `scripts/generate-completions.sh`	`./scripts/generate-completions.sh`

Commit the regenerated files together with the source change. Keep the three templates in sync: same commands, same flags per command, and the same branch-completion behavior (git branches plus special ID 1 for commands that take a worktree target).

Read the full file on GitHub · 59 lines

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 Changed · -86 lines · -585 tokens per session 7e524b65d546
2mo ago First seen · 145 lines · 1,366 tokens per session scan A df64af14c284

Subscribe to this mod's changes

git-worktree-runner completions.instructions.md is an instructions file published in the GitHub repository coderabbitai/git-worktree-runner (1,808 stars, last pushed yesterday), licensed Apache-2.0. It adds 781 tokens to every session, about $0.0031 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-30.

Git and workflow git-worktree

git-worktree-runner completions.instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
git-worktree-runner completions.instructions.mdcoderabbitai/git-worktree-runner	Instructions file	1.8k	yesterday	Apache-2.0	A	781	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

git-worktree-runner: Instructions file for GitHub Copilot