# 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.

- Skill: `majiayu000/gh-create-pr-linked-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/gh-create-pr-linked-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/gh-create-pr-linked-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/majiayu000/gh-create-pr-linked-2

---


# 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

```bash
# 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

1. **Verify changes committed**: `git status` shows clean
2. **Push branch**: `git push -u origin branch-name`
3. **Create PR**: `gh pr create --issue <number>`
4. **Verify link**: Check issue's Development section on GitHub
5. **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:

```bash
# 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-ops`
- `73-fix-memory-leak`
- `105-update-docs`

## References

- See CLAUDE.md for complete git workflow
- See CLAUDE.md for PR submission requirements