lwlee2608/gh-create-pr
skills/gh-create-pr/SKILL.md
Use when creating/raising/opening/submitting a GitHub PR. Produces short, feature-focused descriptions without a test plan.
testing
Updated May 13, 2026
$ install --global
skillsauthnpx skillsauth add lwlee2608/agent-skills gh-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 13, 2026, 7:28 AM254.3s1 file scanned
SKILL.md
- name:
- gh-create-pr
- description:
- Use when creating/raising/opening/submitting a GitHub PR. Produces short, feature-focused descriptions without a test plan.
- user-invocable:
- true
Create a GitHub Pull Request
Create PRs with short, feature-focused descriptions. No test plan or co-author lines.
Rules
- Create the PR using
gh pr createwith a HEREDOC body:gh pr create --title "<short title>" --body "$(cat <<'EOF'
[## Context <1–2 sentences — include this section only if rule 3 applies>
]## Summary <bullet points describing the main features/changes, proportional to PR size> EOF )"
2. **Title**: Use imperative mood (e.g., "Add user auth", "Fix pagination bug").
3. **Context section**: Include `## Context` above `## Summary` only when the PR has business/user-facing motivation sourced from a linked issue, ticket, CLAUDE.md, or conversation. Keep it to 1–2 sentences in plain language — what the user or business gets, not how. **Do not invent or speculate**; omit the section entirely for purely technical work (refactor, chore, dep bump) or when no source material exists.
4. **Summary section**: Bullet points proportional to PR size, focused on the changes themselves.
5. **No test plan**: Do not add a test plan, checklist, or QA section.
6. **No co-author**: Do not add "Co-Authored-By" lines.
Related Skills
lwlee2608/handoff
documentation
VerifiedTrustedCommunity
Use when the user wants to condense the current conversation into a handoff document for another agent to pick up.
SKILL.mdUpdated May 22, 2026
lwlee2608/whiteboard-explain
development
VerifiedTrustedCommunity
Use when the user asks to explain or teach a technical concept. Replies in plain language with a simple diagram instead of a wall of jargon.
SKILL.mdUpdated May 18, 2026
lwlee2608/writing-system-prompts
development
VerifiedTrustedCommunity
Use when writing or editing a system prompt for any LLM API or SDK (any code passing a `system=` / `system` role parameter, or a `.txt`/`.md` file holding such a prompt). Applies prompt-engineering and prompt-caching best practices.
SKILL.mdUpdated May 13, 2026
lwlee2608/prefer-make
tools
VerifiedTrustedCommunity
Use before running any Go toolchain command (`go build`, `go test`, `go run`, `go vet`, `go fmt`, `golangci-lint`). Substitutes make targets when a Makefile is present.
SKILL.mdUpdated Apr 16, 2026