soyio-id/create-pr
skills/create-pr/SKILL.md
Create a clear, review-ready pull request with gh CLI. Gather context from commits, diff, and Linear when available; follow repository templates; push safely; and return the PR URL with merge guidance.
tools
Updated May 14, 2026
$ install --global
skillsauthnpx skillsauth add soyio-id/skills create-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 14, 2026, 4:56 AM175.0s1 file scanned
SKILL.md
- name:
- create-pr
- description:
- Create a clear, review-ready pull request with gh CLI. Gather context from commits, diff, and Linear when available; follow repository templates; push safely; and return the PR URL with merge guidance.
Create Pull Request
Goal
Open a high-quality PR that is easy to review and safe to merge:
- includes only intended changes
- uses a clear title and useful body
- follows repo PR template when present
- links related Linear issues with the correct magic words
- reports final PR status and next actions
Inputs
base_branch(optional, default: repo default branch)is_draft(true/false, default:false)title_hint(optional)extra_context(optional: issue links, rollout notes, risks)
Safety rules
- Never create a PR from
main/masterdirectly. - Never include unrelated unstaged/uncommitted changes.
- Do not rewrite branch history unless explicitly requested.
- If history rewrite is required, use
--force-with-leaseonly. - If a PR already exists for the branch, do not create a duplicate.
Workflow
-
Check prerequisites
gh auth statusgit status --short --branchgit branch --show-current
-
Determine base branch
- Prefer user input.
- Otherwise use repo default branch:
gh repo view --json defaultBranchRef -q .defaultBranchRef.name
-
Review branch content
git log --oneline origin/<base_branch>..HEADgit diff --stat origin/<base_branch>...HEAD- Confirm scope is coherent and PR-ready.
-
Discover related Linear issues
- Use Linear MCP when it is available.
- Search the branch name, commits, title hint, and
extra_contextfor issue IDs such asSOYIO-20. - If issue IDs are found, verify them with Linear MCP and capture their titles/statuses.
- If no issue IDs are found and Linear MCP is available, search Linear using branch/title/commit keywords.
- If Linear MCP is unavailable, use only explicit issue IDs already present in local context and state that Linear lookup was unavailable.
- Never invent issue IDs.
-
Ensure branch is pushed
- If no upstream:
git push -u origin HEAD - Otherwise:
git push
- If no upstream:
-
Build PR content
- Title: concise, outcome-focused; Conventional Commit style preferred.
- Body:
- If
.github/pull_request_template.md(or equivalent) exists, follow it exactly. - Otherwise include: context, summary, testing, risk/rollback, related issue.
- Put related Linear issues in the most relevant template section, or add
## Linearwhen there is no obvious section. - Link each Linear issue with an allowed magic word followed by the ID, for example
closes SOYIO-20. - Use a closing magic word only when this PR fully completes the issue.
- Use a non-closing magic word when this PR is partial, preparatory, informational, or only related.
- Use the magic words from
Magic words reference.
- If
-
Create or reuse PR
- Check existing PR first:
gh pr view --json url,number,state 2>/dev/null
- If existing PR found, return it and summarize status.
- If no PR exists, create it:
- Check existing PR first:
gh pr create --title "<title>" --body "<body>" --base <base_branch>
For draft PR:
gh pr create --title "<title>" --body "<body>" --base <base_branch> --draft
- Post-create checks
gh pr view --json url,number,title,state,mergeStateStatus,reviewDecision- Report CI/review state and what remains before merge.
Validation
- Prefer smallest relevant checks before PR creation (lint/unit/targeted tests).
- Include test commands and concise outcomes in the PR body.
- Verify every Linear issue link uses one allowed magic word followed by the issue ID.
- If checks were not run, state why and call it out explicitly.
Magic words reference
Closing magic words:
close, closes, closed, closing, fix, fixes, fixed, fixing, resolve, resolves, resolved, resolving, complete, completes, completed, completing.
Non-closing magic words:
ref, references, part of, related to, contributes to, towards.
Output format
Return:
- PR number + URL
- base/head branches
- draft or ready status
- merge/check state
- test summary (commands + results)
- related Linear issue links
- recommendation: ready for review, wait for CI, or needs follow-up
Error handling
- If working tree is dirty, ask to commit or stash first.
- If no commits ahead of base, report no PR needed.
- If
ghauth fails, instruct to rungh auth login. - If creation fails due to permissions, report exact error and next step.
Related Skills
soyio-id/using-git-worktrees
tools
VerifiedTrustedCommunity
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
SKILL.mdUpdated Apr 15, 2026
soyio-id/start-parity-workspace
tools
VerifiedTrustedCommunity
Create or reuse a coordinated Soyio parity workspace across soyio, soyio-dashboard, and soyio-embeds, then start the matching local runtimes.
SKILL.mdUpdated Apr 15, 2026
soyio-id/prepare-security-prs
testing
VerifiedTrustedCommunity
Triage and prepare automated dependency security PRs for merge with minimal risk. Identify bot PRs that need intervention, resolve required issues only, refresh stale branches safely, detect superseded PRs, and keep diffs dependency-focused.
SKILL.mdUpdated Apr 15, 2026
soyio-id/fix-vulnerabilities
testing
VerifiedTrustedCommunity
Fix multiple dependency vulnerabilities across multiple repos. Parses Vanta-style vulnerability entries, groups by repo, creates a single fix branch per repo, applies all fixes, verifies compatibility, and creates PRs after user approval. Use when the user says '/fix-vulnerabilities' or asks to fix vulnerabilities across repos.
SKILL.mdUpdated Apr 15, 2026