owainlewis/pr
skills/pr/SKILL.md
Commit, push, and open a pull request with a clear description. Use when finished work on the current branch needs to become a PR.
$ install --global
skillsauthnpx skillsauth add owainlewis/blueprint 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: Jun 12, 2026, 6:31 AM210.5s1 file scanned
SKILL.md
- name:
- pr
- description:
- Commit, push, and open a pull request with a clear description. Use when finished work on the current branch needs to become a PR.
- user-invocable:
- true
- argument-hint:
- [optional: PR title, base branch, or draft|ready]
PR
Take the finished change on the current branch to an open pull request.
Workflow
- Run
branchfirst if still on the default branch. - Run
commitfor any uncommitted intended changes. - Push the branch.
- Open the PR with
ghor GitHub tools. Draft by default; ready only when the user or ticket policy asks. Write the title like a commit subject: in squash-merge repos it becomes the commit on the default branch. - Write the body from the diff and the work actually done, not from memory: what changed and why, ticket link when one exists, tests and checks run with results, review findings fixed, and anything not verified. A reviewer should be able to judge the change without reading the conversation.
- Report the PR URL.
Rules
- One PR per branch. If one is already open, push and update its description instead of opening another. Preserve human edits to the body: update only what the new commits change, never rewrite the whole description.
- Follow the repo's PR template when one exists.
- Do not claim verification that did not run.
- If push or PR creation fails, keep the branch and commit local and report the exact failure.
Related Skills
owainlewis/multitask
development
VerifiedTrustedCommunity
Run several tickets to draft PRs at the same time, one isolated worker per ticket. Use when the user passes multiple tickets and wants them worked in parallel. Composes task-to-pr per ticket; never writes code itself.
143SKILL.mdUpdated Jun 12, 2026
owainlewis/task-to-pr
development
VerifiedTrustedCommunity
Turn one ticket into a draft PR. Use when the user passes a ticket reference (JIRA-123, LIN-123, github#456, an issue URL) and expects code, tests, review, and a PR. Use implement when no PR is expected; use multitask for several tickets at once.
143SKILL.mdUpdated Jun 11, 2026
owainlewis/implement
development
VerifiedTrustedCommunity
Turn one scoped task into a verified diff: code, tests, verification, report. The inner build step of the delivery flow. Use directly when the workspace is prepared and no PR is expected; use task-to-pr when a ticket should become a PR.
143SKILL.mdUpdated May 10, 2026
owainlewis/branch
tools
VerifiedTrustedCommunity
Create a traceable Git branch for the current task.
143SKILL.mdUpdated May 10, 2026