skills.rest
NaoyaMiyagawa
NaoyaMiyagawaCOMMUNITY
Explore all skills by this author →
𝕏@_miya_nm7GitHub

custom-gh-pr-creating-editing

Creates and edits GitHub pull requests with Jira-titled formatting, concise descriptions, and local code review.

1|Updated Apr 3, 2021
Search Tags:#code review#pull request#github#codex#gh cli#jira#pr description
One-click install
npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill custom-gh-pr-creating-editing-naoyamiyagawa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: custom-gh-pr-creating-editing
Source: https://github.com/NaoyaMiyagawa/dotfiles/tree/main/.ai/skills/custom-gh-pr-creating-editing
Command: npx skills add https://github.com/NaoyaMiyagawa/dotfiles --skill custom-gh-pr-creating-editing-naoyamiyagawa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, reviewer-friendly GitHub pull requests is repetitive and error-prone: titles drift from Jira conventions, descriptions become bloated, issue references fail to expand, and self-review gets skipped. This Skill standardizes PR creation and editing so every PR follows the same title format, description structure, and review workflow. ## Core Features & Use Cases - Jira-driven PR titles: Formats titles as [KEY] Title using the Jira issue key from the branch name and the verbatim Jira Summary, with fallback tag conventions for non-Jira work. - Concise structured descriptions: Enforces short motivation-led bodies, bullet-per-line issue/PR references (close:, Previous:, Next:), repository PR template compliance, and collapsible validation-run blocks. - Local second-opinion review: Runs a local Codex CLI code review against the repo's coding-standard skills after creating or editing the PR, instead of posting review-bot mentions. - Use Case: After finishing a feature branch named feature/AN-1000-user-management, ask the assistant to create the PR — it fetches the Jira summary, titles the PR [AN-1000] User Management Page, writes a scannable description with a close: reference, assigns the author, and runs a local Codex review. ## Quick Start Create a GitHub pull request for my current branch following the Jira title format and run the local code review afterward.

Frequently Asked Questions about custom-gh-pr-creating-editing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub PR with a Jira ticket in the title?▼

Format the title as the bracketed Jira issue key followed by the verbatim Jira Summary, for example `[AN-1000] User Management Page`. Extract the key from the branch name and fetch the Summary from Jira before running gh pr create.

How do I make GitHub issue references expand in a PR description?▼

Write each issue or PR reference as its own bullet line starting with `- `, such as `- #123`. Inline references inside sentences do not expand into linked titles, so pull every ref onto its own bullet line.

Does this PR workflow follow the repository pull request template?▼

Yes. It checks for templates at paths like .github/pull_request_template.md and fills every template section, adding references, Jira links, and validation blocks inside the template structure rather than replacing it.

Can I auto-close a GitHub issue from a PR description?▼

Yes. When the changes fully resolve an issue, place `- close: #<issue_number>` at the very top of the description so GitHub auto-closes the issue on merge. Stacked branches add Previous: and Next: reference blocks below it.

Why run a local code review instead of a PR review bot?▼

The repository does not use review bots, so the workflow runs a local Codex CLI review against the repo's coding-standard skills for a second opinion from a different model. It is skipped only when Codex is rate-limited or unauthenticated.

Related Skills

Explore More Software Engineering Skills→
ysoftmanysoftman
9

jira-git-checkout-branch

Create and check out a Jira-based git branch from an In Progress issue.

Community
Advanced
taloncjonestaloncjones

post-merge

Remove Git worktrees and branches, then update linked Jira tickets.

Community
Advanced
jaktestowacjaktestowac
113

documenting-test-suites

Writes README quickstarts, tag glossaries, and architecture decision records for test suites.

Community
Intermediate
team-attentionteam-attention
282

create-pr

Create GitHub pull requests from the current branch using the GitHub PR API.

Official
Advanced