Source profileQuality 71/100Review permissions

dyoshikawa/rulesync/.rulesync/skills/rebase-latest-main/SKILL.md

rebase-latest-main

Fetch latest origin/main and rebase it onto the current branch, resolving conflicts if necessary. Use when the user wants to rebase on main, update their branch with latest main, or sync with upstream.

Source repository stars
1,263
Declared platforms
0
Static risk flags
3
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Fetch the latest origin/main and rebase it onto the current working branch.

Best for

  • Use when the user wants to rebase on main, update their branch with latest main, or sync with upstream.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/dyoshikawa/rulesync --skill ".rulesync/skills/rebase-latest-main"
Safe inspection promptEditorial

Inspect the Agent Skill "rebase-latest-main" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/rebase-latest-main/SKILL.md at commit 310b711fbe8cffc14debb276ade8a384c2b89083. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Step 1: Verify Current State

    1. Check the current branch:

    Check the current branch:Ensure there are no uncommitted changes:Commit them first, or
  2. 02

    Step 2: Fetch Latest Changes

    Fetch the latest changes from the remote:

    Fetch the latest changes from the remote:
  3. 03

    Step 3: Rebase onto origin/main

    1. Identify conflicting files:

    Identify conflicting files:For each conflicting file:Read the file content to understand the conflict
  4. 04

    Step 4: Handle Rebase Failure

    If unable to resolve conflicts automatically:

    Show the conflicting files and conflict markers to the userAsk for guidance on how to resolveIf the user wants to abort:

Permission review

Static risk signals and limitations

Runs scripts

medium · line 10

The documentation asks the agent to run terminal commands or scripts.

git branch --show-current

Runs scripts

medium · line 16

The documentation asks the agent to run terminal commands or scripts.

git status --porcelain

Network access

medium · line 25

The documentation includes network, browsing, or remote request actions.

Fetch the latest changes from the remote:

Reads files

low · line 52

The documentation asks the agent to read local files, directories, or repositories.

Read the file content to understand the conflict

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score71/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars1,263SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
dyoshikawa/rulesync
Skill path
.rulesync/skills/rebase-latest-main/SKILL.md
Commit
310b711fbe8cffc14debb276ade8a384c2b89083
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

Rebase Latest Main

Fetch the latest origin/main and rebase it onto the current working branch.

Step 1: Verify Current State

  1. Check the current branch:

    git branch --show-current

  2. Ensure there are no uncommitted changes:

    git status --porcelain

    If there are uncommitted changes, either:

    • Commit them first, or
    • Ask the user how to proceed (commit, stash, or abort)

Step 2: Fetch Latest Changes

Fetch the latest changes from the remote:

git fetch origin main

Step 3: Rebase onto origin/main

Start the rebase:

git rebase origin/main

If rebase succeeds without conflicts:

Proceed to Step 5.

If conflicts occur:

  1. Identify conflicting files:

    git diff --name-only --diff-filter=U

  2. For each conflicting file:

    • Read the file content to understand the conflict
    • Analyze both versions (HEAD and origin/main)
    • Resolve the conflict by choosing the appropriate changes or merging them
    • Stage the resolved file: 
      git add <resolved-file>

  3. Continue the rebase:

    git rebase --continue

  4. Repeat until all conflicts are resolved and rebase is complete.

Step 4: Handle Rebase Failure

If unable to resolve conflicts automatically:

  • Show the conflicting files and conflict markers to the user
  • Ask for guidance on how to resolve
  • If the user wants to abort: 
    git rebase --abort

Step 5: Push Changes

After successful rebase, force push to update the remote branch:

git push --force-with-lease

Note: --force-with-lease is safer than --force as it prevents overwriting others' work.

Step 6: Report Result

Summarize the operation:

  1. Number of commits rebased
  2. Any conflicts that were resolved
  3. Confirmation that the branch is now up-to-date with origin/main

Alternatives

Compare before choosing

Computed 10042,015

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

2026-07-270 platforms
Computed 10042,015

coreyhaines31/marketingskills

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

2026-07-270 platforms
Computed 997

event4u-app/agent-config

design-review

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

2026-07-280 platforms
Computed 9831,966

K-Dense-AI/scientific-agent-skills

dask

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

2026-07-280 platforms