sync-pr-branch

sync-pr-branch is a skill for Claude Code from stone-w4tch3r/Figma-Context-MCP. It costs 19 tokens per session (332 once invoked), scanned A, original, from a forked repository, MIT.

A procedure for updating a pull-request branch with changes from the main branch of the original repository. A pull request is a proposed code change awaiting review.

In plain words
What is it for?
Use it to merge upstream changes, fix conflicts, run installation, type-checking, build, and test commands, then push the updated branch.
Why use it?
It helps bring an outdated branch up to date, resolve conflicts, run checks, and make the pull request mergeable.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter. Also seen: mentions Claude Code.

Good fit Use it to merge upstream changes, fix conflicts, run installation, type-checking, build, and test commands, then push the updated branch.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add stone-w4tch3r/Figma-Context-MCP --skill sync-pr-branch
Clone the repo
git clone --depth 1 https://github.com/stone-w4tch3r/Figma-Context-MCP

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.

agentmods badge for sync-pr-branch

README.md
[![agentmods](https://agentmods.dev/badge/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch/github.svg)](https://agentmods.dev/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch)
Your own site
<a href="https://agentmods.dev/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch"><img src="https://agentmods.dev/badge/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch/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.

agentmods 80×15 button for sync-pr-branch

Your own site · 80×15
<a href="https://agentmods.dev/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch"><img src="https://agentmods.dev/badge/skills/stone-w4tch3r/figma-context-mcp/sync-pr-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 332 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 fork From a forked repository.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00332
Opus 5 $0.00010 $0.00166
Sonnet 5 $0.00004 $0.00066
Haiku 4.5 $0.00002 $0.00033

Measured 11d ago against content hash 01112731ab76, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

sync-pr-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 11d 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.

skills/sync-pr-branch/SKILL.md · 24 lines

What it actually says

Sync a PR branch with upstream to make it mergeable again.

Prerequisites: Upstream must already be fetched. Run /sync-fork first if the fork's main branch is also behind.

Steps

  1. Identify the PR: gh pr list --state open --repo <upstream> --author <user> or check gh pr view <number>.
  2. Checkout the branch: git checkout <branch> (fetch from origin if needed).
  3. Merge upstream: git merge upstream/main.
  4. Resolve conflicts: Version files (package.json, lockfiles) — take upstream and regenerate. Code conflicts — keep both sides where additive, prefer upstream for structural changes.
  5. Fix post-merge issues: Run pnpm install, pnpm type-check, pnpm build, pnpm test. Fix any breakage (e.g. jest→vitest migration, import changes).
  6. Commit and push: git add -A && git commit then git push origin <branch>.
  7. Verify: gh pr view <number> --repo <upstream> --json mergeable,mergeStateStatus should show MERGEABLE/CLEAN.
  8. Return to main: git checkout main.

STOP and report for complex merge conflicts requiring complex logic understanding and rewriting or breaking API changes.

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.

  1. 11d ago First seen · 24 lines · 19 tokens per session scan A 01112731ab76

Subscribe to this mod's changes

sync-pr-branch is a skill published in the GitHub repository stone-w4tch3r/Figma-Context-MCP (29 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 332 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

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.

rpamis/comet · 72 tokens

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.

zeenie-ai/OpenCompany · 51 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens