How do I install the Gh Create Pr Linked skill?

Run npx skillmds@latest add majiayu000/gh-create-pr-linked in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Create Pr Linked safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Create Pr Linked?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Create Pr Linked free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Create Pr Linked?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Create Pr Linked by majiayu000 — Agent Skill

Name: Gh Create Pr Linked
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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 status shows 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-ops
73-fix-memory-leak
105-update-docs

References

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

---name: gh-create-pr-linkeddescription: 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.--- # 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

Frequently asked questions

Gh Create Pr Linked