Borrowing it
Nothing to install: this file belongs to Parslee-ai/neo. 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/Parslee-ai/neo/main/.claude/commands/sync-branch.mdgit clone --depth 1 https://github.com/Parslee-ai/neoWrote 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/parslee-ai/neo/sync-branch)<a href="https://agentmods.dev/commands/parslee-ai/neo/sync-branch"><img src="https://agentmods.dev/badge/commands/parslee-ai/neo/sync-branch.svg" alt="Measured on agentmods" 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.00023 | $0.00502 |
| Opus 5 | $0.00012 | $0.00251 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
sync-branch 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 7d 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.
What it actually says
Sync Branch with Base
Sync the current branch with the base branch before PR review. You (Claude) will intelligently resolve any merge conflicts.
Workflow
Step 1: Fetch Latest Changes
Fetch the latest changes from origin:
git fetch origin
Step 2: Merge Base Branch
Attempt to merge the base branch:
git merge origin/$BASE_BRANCH --no-edit
Step 3: Handle Conflicts (Claude's Responsibility)
If there are conflicts, YOU (Claude) must resolve them intelligently:
- Check
git statusto see conflicted files - For each conflicted file, review the conflict markers
- Use your understanding of the code to resolve conflicts intelligently
- Stage resolved files with
git add - Complete merge with
git commit --no-edit
If conflicts cannot be resolved (e.g., too complex, unclear intent):
git merge --abort
Then return synced: false with a clear explanation.
Step 4: Push Changes
If the merge was successful (with or without conflicts):
git push origin HEAD
Final Output (STRICT JSON)
{
"synced": true|false,
"had_conflicts": true|false,
"summary": "Brief summary of sync result"
}
Examples:
- Success without conflicts:
{"synced": true, "had_conflicts": false, "summary": "Branch synced with main, no conflicts"} - Success with resolved conflicts:
{"synced": true, "had_conflicts": true, "summary": "Branch synced with main, resolved conflicts in 2 files"} - Aborted due to conflicts:
{"synced": false, "had_conflicts": true, "summary": "Aborted merge with main: conflicts in config.json require manual resolution"} - Failure:
{"synced": false, "had_conflicts": false, "summary": "Failed to fetch from origin"}
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.
- 7d ago First seen · 73 lines · 23 tokens per session scan A 0cb18da057f1
sync-branch is a command published in the GitHub repository Parslee-ai/neo (16 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 502 once invoked, about $0.0001 per session on Opus 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
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.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.