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
npx -y skills add kbrovibes/bro-toolkit --skill pullAssembled 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 pullwithout--rebase— the user wants linear history. - Don't
git reset --hardto "recover" from a failed rebase. Stop and tell the user. - Don't push.
- Don't switch branches.
- Don't run
git gcor 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.
Gives 0 of the 12 instructions most pr commit review skills give in 496 tokens
Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07
- Use conventional commits formatin 127 of 888, across 115 files
- Keep subject line under 72 charactersin 62 of 888, across 48 files
- Delete branches after mergein 51 of 888, across 38 files
- Use imperative mood in subject linein 51 of 888, across 42 files
- Use imperative mood in commit messagesin 44 of 888
- Verify directory is ignored before creating worktreein 43 of 888, across 12 files
- Generate a conventional commit messagein 43 of 888
- Add unignored worktree directories to gitignorein 42 of 888, across 10 files
- Make atomic commitsin 39 of 888, across 27 files
- Run tests before committingin 36 of 888, across 25 files
- Verify clean test baselinein 35 of 888, across 9 files
- Split unrelated changes into separate commitsin 35 of 888, across 30 files
Said here and by no other author read
- confirm you are in a git repository
- stop on unresolved merge or rebase markers
- ask the user if upstream is unset
- run git pull with rebase and autostash
- report autostash reapplication status
- report cause and next step on failure
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.