pablogore/shipwright/branch-pr
Claude Code and agent skill by pablogore/shipwright
- community
Checking that the SKILL.md file is still in the repository.
Create Shipwright pull requests on Git Flow branches with issue-first discipline. Trigger: creating, opening, or preparing PRs for review.
Install
npx vskill@latest install pablogore/shipwright/branch-prSKILL.md
The same SKILL.md was published earlier as pablogore/shipwright/branch-pr.
When to Use
Use this skill when:
- Creating a pull request for any change to this repository
- Preparing a branch for submission
- Helping a contributor open a PR against
developormain
Critical Rules
- This repo uses Git Flow, not GitHub Flow — branch from
develop, never commit directly tomainordevelop. - Link the driving issue in the PR body (
Closes #N/Fixes #N/Resolves #N) whenever an issue exists — this repo does not currently run automated issue-link enforcement, so treat it as required discipline, not a gate you can rely on CI to catch. - A PR touching a public pipeline contract requires an SDD change backing it (see
openspec/changes/). If the diff changes provider YAML shape, step contracts, or plugin interfaces underinternal/interfaces/, confirm an approvedopenspecchange exists before opening the PR. - Hotfixes target `main` directly and bypass
develop; because of that, CI runs full validation on hotfix branches (see.github/workflows/ci.yml). Everything else targetsdevelop. - No `Co-Authored-By` / AI attribution trailers in commits or PR descriptions — conventional commits only.
Branch Naming (Git Flow)
Branch from develop (or main for hotfixes only):
| Type | Branch pattern | Base | Example | |
|---|---|---|---|---|
| Feature | feature/<description> | develop | feature/plugin-retry-policy | |
| Bug fix | fix/<description> | develop | fix/yaml-step-parsing | |
| Hotfix | hotfix/<description> | main | hotfix/registry-auth-panic | |
| Chore | chore/<description> | develop | chore/bump-dagger-sdk |
Format: type/description — lowercase, hyphen-separated, no spaces.
Conventional Commits
Commit messages should follow:
type — one of: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test. Use ! after the type for a breaking change (feat!: ...).
PR Body Checklist
There is no repository-provided PULL_REQUEST_TEMPLATE.md in this repo, so build the body from these sections:
- Linked issue —
Closes #Nwhen an issue exists. - Summary — 1-3 bullets of what changed and why.
- Changes — table of touched paths and what changed in each.
- SDD reference — if the PR implements or completes an
openspecchange, link the change folder underopenspec/changes/<change-id>/. - Test plan — exact commands run locally (see the
shipwright-testingskill) and their result, including local/CI parity confirmation when Dagger-executed steps are involved. - Rollback — what reverting this PR removes, and whether it's isolated.
Commands
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/branch-pr/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/pablogore/shipwright/branch-pr)