Pr
- 2 installs
- 8k repo stars
- Updated August 4, 2026
- getstream/vision-agents
Creates a draft pull request for the Vision-Agents repo with the gh CLI, following the repo PR template and checking for multiple logical changes.
About
Opens a draft GitHub pull request for the Vision-Agents repo using the gh CLI and the repo's PR template. A developer uses it after pushing a branch to produce a well-structured PR body summarizing every commit.
- Runs the repo check and stops to ask about splitting branches with more than one logical change
- Always creates the PR as a draft and follows the pull_request_template.md
Pr by the numbers
- 2 all-time installs (skills.sh)
- Ranked #498 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/getstream/vision-agents --skill prAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 8k |
| Last updated | August 4, 2026 |
| Repository | getstream/vision-agents ↗ |
What it does
Creates a draft pull request for the Vision-Agents repo with the gh CLI, following the repo PR template and checking for multiple logical changes.
Files
Pull Request (Vision-Agents)
Before creating
- Run
git log main..HEAD --oneline. If the branch contains more than one independent logical change, STOP and ask the user whether to split it before proceeding. - Run
uv run --no-sync dev.py check. Skip if the diff does not touch Python code (*.py) orpyproject.toml— e.g. docs-only,.gitignore,.github/, or.claude/changes. - Do not run integration tests locally, CI handles them.
- If the change is user-facing (public API break, new feature, bug fix), update
CHANGELOG.mdper the rules inCLAUDE.md.
Creating
- Always
gh pr create --draft. Push the branch first. - Follow
.github/pull_request_template.md. Read every commit on the branch, do not summarise from the latest commit alone. ## Whyis motivation + context.## Changes, if included, is high-level; never per-bullet justifications, those belong in## Why.- Link public GitHub issues inline within
## Why(e.g. "users reported X (#478)"), not as a trailingFixes #N. - Do not paste CI, lint, or tool output in the body.
- Do not hard-wrap paragraphs. GitHub renders each newline inside a paragraph as a visible line break, so a 72-column-wrapped paragraph becomes a staircase. Write each paragraph or bullet as one unbroken line; rely on the browser to soft-wrap. Only use newlines to separate paragraphs, list items, or block elements.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148