gh-create-pr-linked
Create a pull request properly linked to a GitHub issue using gh pr create --issue. Use when creating a PR that implements or addresses a specific issue.
When & Why to Use This Skill
This Claude skill automates the creation of GitHub Pull Requests and ensures they are properly linked to existing issues using the GitHub CLI. It streamlines the development workflow by maintaining strict traceability between code changes and task requirements, helping teams manage their repositories with better visibility and automated issue closing.
Use Cases
- Linking implementation work to specific bug reports or feature requests to ensure a clear audit trail in GitHub's development section.
- Automating the PR creation process immediately after completing a task on a feature branch to reduce manual CLI overhead.
- Standardizing repository management by enforcing issue-linking requirements, ensuring that every PR contributes to the resolution of a tracked task.
| name | gh-create-pr-linked |
|---|---|
| description | "Create a pull request properly linked to a GitHub issue using gh pr create --issue. Use when creating a PR that implements or addresses a specific issue." |
| category | github |
| agent | implementation-engineer |
Create PR Linked to Issue
Create a pull request with automatic issue linking.
When to Use
- After completing implementation work
- Ready to submit changes for review
- Need to link PR to GitHub issue
- Starting from a feature branch
Quick Reference
# Create PR linked to issue (preferred)
gh pr create --issue <issue-number>
# With custom title and body
gh pr create --title "Title" --body "Closes #<issue-number>"
# Verify link appears
gh issue view <issue-number> # Check Development section
Workflow
- Verify changes committed:
git statusshows clean - Push branch:
git push -u origin branch-name - Create PR:
gh pr create --issue <number> - Verify link: Check issue's Development section on GitHub
- Monitor CI: Watch checks with
gh pr checks
PR Requirements
- ✅ PR must be linked to GitHub issue
- ✅ All changes committed and pushed
- ✅ Branch has upstream tracking
- ✅ Clear, descriptive title
- ✅ Summary in description
- ❌ Do NOT create PR without issue link
Error Handling
| Problem | Solution |
|---|---|
| No upstream branch | git push -u origin branch-name |
| Issue not found | Verify issue number exists |
| Auth failure | Run gh auth status |
| Link not appearing | Add "Closes #ISSUE-NUMBER" to body |
Verification
After creating PR:
# View PR details
gh pr view <pr-number>
# Check CI status
gh pr checks <pr-number>
# Verify issue link
gh issue view <issue-number> # Look for "Development" section
Branch Naming Convention
Format: <issue-number>-<description>
Examples:
42-add-tensor-ops73-fix-memory-leak105-update-docs
References
- See CLAUDE.md for complete git workflow
- See CLAUDE.md for PR submission requirements