Force Push Downstream Skill for Claude

'Force-push a branch and all its downstream branches to origin. Auto-detects push downstream, push chain, push all branches.'

855 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

3472

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/brave/brave-core --skill force-push-downstream

The instruction itself

11 sections, as written by the author

Force Push Downstream

Force-push a branch and all its downstream branches to their respective remotes.

Skips branches whose local and remote tips already match.

Arguments

starting-branch (optional) — The branch to start from. Defaults to the

current branch if not specified.

Examples:

/force-push-downstream — push current branch + all downstream
/force-push-downstream candle-service-webui — push from that branch down

Current State

Branch: !git branch --show-current
Status: !git status --short

Steps

1. Determine starting branch

If an argument was provided, use it as the starting branch. Otherwise use the

current branch.

git branch --show-current

2. Detect downstream chain

Run the detect-chain script (shared with rebase-downstream) to find all

downstream branches:

bash .claude/skills/rebase-downstream/detect-chain.sh <starting-branch>

3. Build push list

The push list is: the starting branch itself, followed by every downstream

branch in tree order (from detect-chain output).

4. Show plan and confirm

Display the branches that will be pushed:

Force push plan:
  candle-service-background-webcontents
    → background-webcontents-timer
      → candle-service-webui
        → candle-service-model-loading
          → brave-history-embeddings
          → local-ai-internals

For each branch, check if it is already up-to-date with origin:

# Get local and remote SHAs
local_sha=$(git rev-parse <branch>)
remote_sha=$(git rev-parse origin/<branch> 2>/dev/null || echo "none")

If local_sha == remote_sha, mark as (up-to-date, will skip). If the remote

branch doesn't exist, mark as (new, will push). Otherwise mark as

(diverged, will force-push).

Ask the user to confirm before pushing.

5. Push each branch

For each branch in the push list:

Skip if up-to-date: If local SHA matches origin SHA, print skip message

and move on.

Force push:

   git push --force-with-lease origin <branch>

Use --force-with-lease for safety — it fails if someone else pushed to the

remote since our last fetch, preventing accidental overwrites of others'

work.

If the remote branch doesn't exist (first push), use:

   git push -u origin <branch>

Report result: Print success/failure for each branch.

6. Report summary

After all pushes complete, show a summary:

Force push results:
  ✓ candle-service-background-webcontents (pushed)
  - background-webcontents-timer (skipped, up-to-date)
  ✓ candle-service-webui (pushed)
  ✓ candle-service-model-loading (pushed)
  ✓ brave-history-embeddings (pushed, new)
  ✗ local-ai-internals (failed: ...)

Important

Always use --force-with-lease instead of --force for safety
Do NOT push without user confirmation
Skip branches that are already up-to-date (local == remote SHA)
If any push fails, report it but continue with remaining branches
Return to the original branch at the end

Other skills for the same job

different authors, same section of the catalogue

MCP Builder

by anthropics

vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens

Finishing A Development Branch

by ZhanlinCui

×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Vercel React Native Skills

by vercel-labs

vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens

Vercel React Best Practices

by ratacat

×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take brave/force-push-downstream from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.