Skip to content
TrustedSkillsbeta
Back to all skills

Git Rebase Patterns

Checked
laurigates·vlatest·backend·MIT

Helps with Git, patterns as part of agent workflows workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add laurigates/claude-plugins --skill git-rebase-patterns -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

laurigates

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned laurigates/claude-plugins at 45d1d7dcf6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
45d1d7dcf6
Manifest
git-plugin/skills/git-rebase-patterns/SKILL.md
Scanned
1 file, 291 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The git-rebase-patterns skill enables AI agents to identify and apply specific rebase strategies, such as interactive rebasing or cherry-picking, to streamline commit histories. It helps automate complex Git workflows by suggesting optimal patterns for squashing, rewriting, or integrating changes across branches.

When to use it

  • Cleaning up a messy feature branch before merging into the main development line.
  • Resolving conflicting commits between two divergent branches without creating merge artifacts.
  • Squashing multiple small, incremental commits into a single logical change for cleaner history.
  • Reordering or reapplying specific commits to align with a new project structure.

Key capabilities

  • Analyzes current branch topology to recommend safe rebase approaches.
  • Generates step-by-step commands for interactive rebasing and conflict resolution.
  • Identifies opportunities to squash related changes into unified commits.
  • Suggests cherry-pick sequences to port specific fixes or features between branches.

Example prompts

  • "I have 15 small commits on my feature branch; suggest a rebase pattern to consolidate them into three logical commits."
  • "My main branch has new changes that conflict with my local work. What is the safest rebase strategy to integrate them?"
  • "Generate a sequence of git commands to cherry-pick only the bug fixes from branch A into branch B, excluding unrelated feature work."

Tips & gotchas

Ensure you are working on a detached branch or have stashed your changes before attempting any history rewriting operations. Always test rebase patterns on a local copy first, as rebasing cannot be undone once pushed to a shared remote repository.