ebkn/create-pr
root/.claude/skills/create-pr/SKILL.md
Create a GitHub pull request with context-aware description
$ install --global
skillsauthnpx skillsauth add ebkn/dotfiles 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: Apr 24, 2026, 8:53 PM1.9s1 file scanned
SKILL.md
- name:
- create-pr
- description:
- Create a GitHub pull request with context-aware description
- allowed-tools:
- Bash(git status *), Bash(git diff *), Bash(git log *), Bash(git rev-parse *), Bash(git push *), Bash(gh repo view *), Bash(gh pr create *), Bash(echo *), Read, Glob, Grep, AskUserQuestion
Pre-fetched context
!git rev-parse --abbrev-ref HEAD
!git status --short
!git ls-files ':(top,icase).github/pull_request_template.md' ':(top,icase).github/pull_request_template/*.md' ':(top,icase)pull_request_template.md'
Instructions
Create a pull request. Follow this flow:
-
Gather context: Get default branch via
gh repo view --json defaultBranchRef -q .defaultBranchRef.name, then rungit log --oneline,git diff --stat, andgit diffagainst it. -
Uncommitted changes: If
git statusabove shows output, ask the user whether to commit them, ignore them, or abort. Do not proceed until answered. -
PR template:
- If a template path is listed,
Readit before writing title/body. - Detect
template_languagefrom headings/instructions/checklists (ignore code, URLs, HTML comments). - Keep template headings/order and keep HTML comments (
<!-- -->). - If no template exists, skip.
- If a template path is listed,
-
Compose PR:
- Title: Conventional Commits.
- Decide title language before drafting and keep it fixed unless the user requests a change.
- Title language policy: use
template_languagefirst whenever it can be detected. - If the user explicitly asks to override language for the current PR, follow that override.
- If no
template_languageis detected, use: explicit user request > latest substantive user message > English. - Ignore slash commands (for example
/create-pr), code blocks, file paths, and URLs when inferring language. - If language signals conflict or are ambiguous, ask the user which language to use before drafting.
- Keep
type(scope)tokens standard (feat,fix, etc.); localize only the description text. - Body: if template exists, fill its sections. If not, use Summary / Changes / Concerns / References.
- Proactively include any reference links (issues, docs, related PRs) found in conversation history.
-
Confirm: Show the full PR title and body. Ask if the user wants to add links or make any edits — apply and re-confirm. Do not push or create until approved.
-
Push and create: Push (
git push -u origin HEAD) only if there are unpushed commits (git log @{upstream}..HEAD). Create withgh pr create --title "<title>" --body "<body>". Return the PR URL.
Related Skills
ebkn/init-project
development
VerifiedTrustedCommunity
Scaffold a new project in the current directory — git init, README.md, CLAUDE.md, Claude settings.json, and linter config for the specified language (TypeScript, Go, Python). Use this skill when the user wants to initialize or bootstrap a new project from scratch, set up a fresh repo, or scaffold project boilerplate.
8SKILL.mdUpdated Apr 17, 2026
ebkn/commit
tools
VerifiedTrustedCommunity
Stage and commit changes with conventional commits
8SKILL.mdUpdated Apr 15, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/extensions/lobster
tools
VerifiedTrustedCommunity
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
357,764SKILL.mdUpdated Apr 10, 2026