gh-create-pr
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.
More from lwlee2608/agent-skills
ascii-diagram
Use after generating or editing ASCII art, box diagrams, tables, or any monospace text art to ensure all lines, corners, and boxes are properly aligned.
30prefer-make
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.
30gh-update-pr
Use when updating GitHub PR title or body. Works around the gh pr edit GraphQL bug caused by GitHub's Projects Classic deprecation.
29create-skill
Use when creating a new agent skill. Ensures the skill follows quality guidelines for SKILL.md files.
25linear
Use when the user wants to interact with Linear.app — reading or searching issues/tickets.
21writing-system-prompts
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.
10