lwlee2608/agent-skills

gh-create-pr

Use when creating/raising/opening/submitting a GitHub PR. Produces short, feature-focused descriptions without a test plan.

First seen Mar 9, 2026

Installation

$ npx skills add lwlee2608/agent-skills --skill gh-create-pr

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from lwlee2608/agent-skills · top by installs.

npx skills add lwlee2608/agent-skills

Browse all from lwlee2608/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,359 B
  • docs SUMMARY.md 143 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 94 installs

SKILL.md

Create a GitHub Pull Request

Create PRs with short, feature-focused descriptions. No test plan or co-author lines.

Rules

  1. Create the PR using gh pr create with a HEREDOC body:

```bash 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 )" ```

  1. Title: Use imperative mood (e.g., "Add user auth", "Fix pagination bug").
  2. 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.
  3. Summary section: Bullet points proportional to PR size, focused on the changes themselves.
  4. No test plan: Do not add a test plan, checklist, or QA section.
  5. No co-author: Do not add "Co-Authored-By" lines.