Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

remote-diff

Estrelas2.393

Forks774

Atualizado11 de junho de 2026 às 16:26

Compare local branch changes against the remote branch to detect rebase/merge mistakes.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

ryanb

ryanb/dotfiles

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	remote-diff
description	Compare local branch changes against the remote branch to detect rebase/merge mistakes.
user-invocable-only	true
allowed-tools	Bash, Read, Glob, Grep, Agent
argument-hint	["base-branch"]

Remote Diff

Compare local branch changes against the remote branch to detect rebase/merge mistakes.

Step 1: Determine base branch

Determine the base branch in this order:

Use $ARGUMENTS if the user specifies a branch
Use the tracked parent from git config branch.$(git branch --show-current).parent, if set and it still resolves to a commit
Use bin/base-branch if the script exists and is executable
Fall back to develop

Step 2: Check prerequisites

Verify the upstream tracking branch exists:

git rev-parse --verify @{u}

If this fails, report that there's no remote branch to compare against and stop. The user needs to push their branch first.

Ensure the tmp directory exists:

mkdir -p tmp

Step 3: Generate and compare diffs

Fetch the latest remote refs, generate both diffs with zero context lines and ignoring whitespace changes, strip metadata lines, then compare:

git fetch origin

git diff -b --unified=0 <base-branch>...HEAD > tmp/local_branch_diff.patch
git diff -b --unified=0 origin/<base-branch>...@{u} > tmp/remote_branch_diff.patch

grep -v -E '^(index |@@ |diff --git)' tmp/local_branch_diff.patch > tmp/local_stripped.patch
grep -v -E '^(index |@@ |diff --git)' tmp/remote_branch_diff.patch > tmp/remote_stripped.patch

diff tmp/local_stripped.patch tmp/remote_stripped.patch > tmp/diff_comparison.patch || true

Step 4: Analyze results

Read tmp/diff_comparison.patch.

If it's empty, report: Clean rebase — no issues detected. The local and remote branches make identical code changes relative to the base branch.

If there are differences, read the relevant source files for context and report:

Interpreting differences

Any difference warrants review. Read the source files to assess each one.

Signs of trouble:

A + line present in the remote diff but missing from local → an addition was lost during rebase
A - line present in the remote diff but missing from local → a deletion was lost, meaning removed code came back
Lines present only in the local diff could be conflict resolution or accidental — verify by reading the code

Report format

For each difference:

What changed — which file and what code differs
Remote version — what the remote branch had
Local version — what the local branch has
Assessment — whether this looks intentional (e.g., correct conflict resolution adapting to renamed code) or suspicious (e.g., lost code, accidental reversion, duplicated changes)

Summary

Overall assessment: clean rebase or needs attention
Any lost or accidentally reverted changes
Any suspicious conflict resolutions

Step 5: Clean up

rm -f tmp/local_branch_diff.patch tmp/remote_branch_diff.patch tmp/local_stripped.patch tmp/remote_stripped.patch tmp/diff_comparison.patch

Mais deste repositório

mesmo repositório

review-queue

ryanb/dotfiles

Show pull requests that need review, ranked by ease of review. Displays PRs as clickable links with line counts, grouped as a dependency tree when PRs build on each other.

2026-07-202.4k

rebase

ryanb/dotfiles

Interactive rebase onto a base branch, resolving conflicts along the way and verifying tests pass. Compares against remote when done.

2026-07-102.4k

pr-feedback

ryanb/dotfiles

Evaluate unresolved review comments on the current branch's PR and, after user confirmation, address each in a separate sub-agent and separate commit.

2026-06-232.4k

interview

ryanb/dotfiles

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Like grill-me, but asks one structured, numbered question at a time with multiple-choice options. Use when the user wants a disciplined interview to stress-test a plan or design, or mentions "interview me".

2026-06-232.4k

pr-pending-feedback

ryanb/dotfiles

Evaluate pending (unsubmitted) review comments on the current branch's PR and, after user confirmation, address each in a separate sub-agent and separate commit.

2026-06-172.4k

fix-all

ryanb/dotfiles

Run bin/claude-review --print and automatically fix all reported issues, committing each fix individually.

2026-06-172.4k

name	remote-diff
description	Compare local branch changes against the remote branch to detect rebase/merge mistakes.
user-invocable-only	true
allowed-tools	Bash, Read, Glob, Grep, Agent
argument-hint	["base-branch"]

Remote Diff

Compare local branch changes against the remote branch to detect rebase/merge mistakes.

Step 1: Determine base branch

Determine the base branch in this order:

Use $ARGUMENTS if the user specifies a branch
Use the tracked parent from git config branch.$(git branch --show-current).parent, if set and it still resolves to a commit
Use bin/base-branch if the script exists and is executable
Fall back to develop

Step 2: Check prerequisites

Verify the upstream tracking branch exists:

git rev-parse --verify @{u}

If this fails, report that there's no remote branch to compare against and stop. The user needs to push their branch first.

Ensure the tmp directory exists:

mkdir -p tmp

Step 3: Generate and compare diffs

Fetch the latest remote refs, generate both diffs with zero context lines and ignoring whitespace changes, strip metadata lines, then compare:

git fetch origin

git diff -b --unified=0 <base-branch>...HEAD > tmp/local_branch_diff.patch
git diff -b --unified=0 origin/<base-branch>...@{u} > tmp/remote_branch_diff.patch

grep -v -E '^(index |@@ |diff --git)' tmp/local_branch_diff.patch > tmp/local_stripped.patch
grep -v -E '^(index |@@ |diff --git)' tmp/remote_branch_diff.patch > tmp/remote_stripped.patch

diff tmp/local_stripped.patch tmp/remote_stripped.patch > tmp/diff_comparison.patch || true

Step 4: Analyze results

Read tmp/diff_comparison.patch.

If it's empty, report: Clean rebase — no issues detected. The local and remote branches make identical code changes relative to the base branch.

If there are differences, read the relevant source files for context and report:

Interpreting differences

Any difference warrants review. Read the source files to assess each one.

Signs of trouble:

A + line present in the remote diff but missing from local → an addition was lost during rebase
A - line present in the remote diff but missing from local → a deletion was lost, meaning removed code came back
Lines present only in the local diff could be conflict resolution or accidental — verify by reading the code

Report format

For each difference:

What changed — which file and what code differs
Remote version — what the remote branch had
Local version — what the local branch has
Assessment — whether this looks intentional (e.g., correct conflict resolution adapting to renamed code) or suspicious (e.g., lost code, accidental reversion, duplicated changes)

Summary

Overall assessment: clean rebase or needs attention
Any lost or accidentally reverted changes
Any suspicious conflict resolutions

Step 5: Clean up

rm -f tmp/local_branch_diff.patch tmp/remote_branch_diff.patch tmp/local_stripped.patch tmp/remote_stripped.patch tmp/diff_comparison.patch