Pull

Skill kbrovibes/bro-toolkit/claude/skills/pull

Update the current git checkout safely. Runs `git pull --rebase --autostash` from the repo root, refusing to proceed if there are unresolved conflicts or detached HEAD. Use when the user says "pull", "/pull", "rebase from origin", or "update this repo".From its SKILL.md

Install

npx -y skills add kbrovibes/bro-toolkit --skill pull

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 496 tokens by cl100k_base, as published. Nobody here has run it

pull

Bring the current git checkout up to date with its upstream — without losing local work or stomping a half-finished rebase.

When to use

Trigger this skill when the user asks to:

"pull", "/pull"
"rebase against main/origin"
"update this checkout"
"sync with upstream"

If you're not in a git repo, say so and stop.

What to do

Run these checks in order. Stop and report at the first failure — never push through.

Confirm git repo. git rev-parse --git-dir — if it fails, say "not a git repo" and stop.
Confirm clean-enough working tree. git status --porcelain — if any output, decide:
- Untracked files only: fine, proceed.
- Modified/staged files: tell the user, then proceed with --autostash.
- Unresolved merge/rebase markers (<<<<<<<): stop and tell the user to resolve first.
Check current branch. git symbolic-ref --short HEAD — if detached HEAD, stop and say so.
Check upstream is set. git rev-parse --abbrev-ref --symbolic-full-name @{u} — if missing, ask the user which remote/branch to pull from (don't guess).
Pull with rebase + autostash: git pull --rebase --autostash.
Summarize. Report: starting commit → ending commit (short SHAs), number of commits applied, any auto-stash that was reapplied.

What not to do

Don't git pull without --rebase — the user wants linear history.
Don't git reset --hard to "recover" from a failed rebase. Stop and tell the user.
Don't push.
Don't switch branches.
Don't run git gc or any other "cleanup."

Output format

Keep it tight — 3 lines max on success:

pulled <N> commit(s) from <upstream>
  <oldsha>..<newsha>  on <branch>
  (autostash: <reapplied|n/a>)

On failure, one line of cause + one suggested next step.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.