Borrowing it
Nothing to install: this file belongs to alleneubank/claude-code. 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/alleneubank/claude-code/main/.claude/skills/git-rebase-sync/SKILL.mdgit clone --depth 1 https://github.com/alleneubank/claude-codeWrote 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/skills/alleneubank/claude-code/git-rebase-sync)<a href="https://agentmods.dev/skills/alleneubank/claude-code/git-rebase-sync"><img src="https://agentmods.dev/badge/skills/alleneubank/claude-code/git-rebase-sync/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/skills/alleneubank/claude-code/git-rebase-sync"><img src="https://agentmods.dev/badge/skills/alleneubank/claude-code/git-rebase-sync.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.00022 | $0.01622 |
| Opus 5.5 | $0.00009 | $0.00649 |
| Sonnet 5.5 | $0.00004 | $0.00324 |
| Haiku 4.5 | $0.00002 | $0.00162 |
Grade A, and why
git-rebase-sync 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git-rebase-sync
Use this skill when you need to sync a feature branch onto the latest origin/{base_branch} via git rebase, including conflict resolution with explicit clarification questions when intent is ambiguous.
Goals
- Rebase the current branch onto a specified base branch (often the repo default branch like
devormain). - Resolve conflicts deliberately, without guesswork.
- Keep safety rails: backup ref, confirmations before history-rewriting commands, and safe pushing.
Hard Rules
- Do not create or switch to a different feature branch. Operate on the current branch name unless I explicitly ask otherwise.
- Before any history-rewriting command (
git rebase ...,git push --force*), print the exact command(s) you will run and wait for my confirmation. - Create a local backup ref (prefer an annotated tag) before starting the rebase. Do not push backup refs unless I explicitly ask.
- Prefer
git push --force-with-lease, never plain--force. - If the correct conflict resolution is unclear, stop and ask a targeted question. Do not invent product behavior.
Workflow
1) Identify base + branch
- Determine the current branch:
git branch --show-current
- Determine the base branch you will rebase onto:
- If not provided, use GitHub default branch:
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
- If not provided, use GitHub default branch:
- Fetch latest:
git fetch origin
2) Preflight safety checks
- Ensure the working tree is clean and there is no operation in progress:
git status
- If
git statusindicates an in-progress merge/rebase/cherry-pick, stop and ask what to do (abort vs continue).
3) Create a local backup ref (do not push)
- Create an annotated tag at current
HEAD:git tag -a {branch_name}-rebase-backup-$(date +%Y%m%d-%H%M%S) -m "pre-rebase backup" HEAD
- Record the tag name as
{backup_ref}for recovery.
4) Choose rebase mode (normal vs preserve merges)
- Check whether the branch contains merge commits:
git rev-list --count --merges origin/{base_branch}..HEAD
- If merge commits exist, ask whether to preserve them (
--rebase-merges) or flatten them (plain rebase).
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 · 122 lines · 22 tokens per session scan A eabf87409e16
git-rebase-sync is a skill published in the GitHub repository alleneubank/claude-code (50 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 1,622 once invoked, about $0.0001 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 skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.