Borrowing it
Nothing to install: this file belongs to fotoetienne/gru. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fotoetienne/gru/main/.claude/commands/rebase.mdgit clone --depth 1 https://github.com/fotoetienne/gruWrote 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.
[](https://agentmods.dev/commands/fotoetienne/gru/rebase)<a href="https://agentmods.dev/commands/fotoetienne/gru/rebase"><img src="https://agentmods.dev/badge/commands/fotoetienne/gru/rebase/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.
<a href="https://agentmods.dev/commands/fotoetienne/gru/rebase"><img src="https://agentmods.dev/badge/commands/fotoetienne/gru/rebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00011 | $0.00513 |
| Opus 5.5 | $0.00004 | $0.00205 |
| Sonnet 5.5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
rebase 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebase the current working branch onto the default branch (usually main) with intelligent conflict resolution.
This command uses the git-rebase skill to:
- Fetch the latest default branch from origin
- Rebase your current branch onto it
- Intelligently resolve merge conflicts by examining PR and issue context
- Report any conflicts that require your input with detailed analysis
Prerequisites
- You must be on a branch (not the default branch)
- Your working directory should be clean (commit or stash changes first)
- You're in a git repository
Workflow
Invoke the git-rebase skill to handle the entire rebase process:
skill: git-rebase
The skill will:
- ✅ Verify your git state
- ✅ Fetch the latest default branch
- ✅ Start the rebase process
- ✅ Resolve straightforward conflicts automatically
- ✅ Pause and ask for input on ambiguous conflicts
- ✅ Provide detailed context from your PR and issue
- ✅ Complete the rebase or report what needs your decision
What Happens During Rebase
Automatically Resolved Conflicts
The skill handles these confidently:
- Independent changes in different code sections
- Import additions (merges and sorts them)
- Refactoring on default branch (adapts your code)
- Both branches adding tests/config (merges both)
Conflicts Requiring Your Input
The skill will pause for:
- Logic conflicts with different approaches
- Security or permission changes
- Architectural decisions
- Configuration value conflicts
- Anything ambiguous or uncertain
When paused, you'll receive:
- Clear explanation of each conflict
- Context from your PR/issue
- Why the skill is uncertain
- Resolution options
- How to relaunch with your decision
After Rebase Completes
- Review the changes:
git diff origin/main - Run tests: Ensure nothing broke
- Force push (if needed):
git push --force-with-lease
If Something Goes Wrong
You can always abort the rebase:
git rebase --abort
This returns you to the state before the rebase started.
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 · 81 lines · 11 tokens per session scan A cd31b8fa9311
rebase is a command published in the GitHub repository fotoetienne/gru (11 stars, last pushed 27d ago), licensed Apache-2.0. It adds 11 tokens to every session and 513 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-30.
Other commands, from other repositories
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
careful
Blocks destructive shell commands once invoked: a PreToolUse Bash guard denies rm -rf outside temp dirs, force pushes and remote branch deletes, git reset --hard, DROP TABLE / DROP DATABASE / TRUNCATE, kubectl delete and terraform or tofu destroy, including inside ssh remote commands, and makes Claude ask the…
Checkpoint Commit
Commit changes at meaningful checkpoints throughout the workflow.
reconcile
Establish git ground truth (branch, status, stashes, worktrees, ahead/behind) before any mutation, halt on protected or destructive operations, then carry the known-good state through a single-concern commit, a push, an open PR, and — after the PR merges — a fast-forward of the default branch. Enforces Law 1 (Research…