skills.rest
penpot
penpotOFFICIAL
Explore all skills by this author →
Website𝕏@penpotappGitHub

gh-issue-from-pr

Create a GitHub issue from a PR with milestone, project, labels, and issue type.

58.3k|3.9k|Updated Dec 29, 2015
Search Tags:#automation#workflow#github#pr#gh#labels#issue-tracking
One-click install
npx skills add https://github.com/penpot/penpot --skill gh-issue-from-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-issue-from-pr
Source: https://github.com/penpot/penpot/tree/main/.opencode/skills/gh-issue-from-pr
Command: npx skills add https://github.com/penpot/penpot --skill gh-issue-from-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a user-facing GitHub issue from a PR by separating the WHAT from the HOW, ensuring the user-visible problem and changes are tracked without embedding implementation details, and applying the correct milestone, project, labels, and issue type.

Core Features & Use Cases

  • Generate a tracking issue from a PR for changelog purposes and release notes.
  • Extract the user-facing problem or feature from the PR body, keeping internal details in the PR.
  • Auto-assign milestone, project, labels, and issue type based on PR metadata and conventions.

Quick Start

Run the gh-issue-from-pr workflow on a target PR in penpot/penpot to generate a corresponding user-facing tracking issue.

Frequently Asked Questions about gh-issue-from-pr

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

FAQPage Schema
How do I create a GitHub issue from a PR for changelog tracking?▼

Generating a tracking issue from a PR separates the user-facing changes from internal implementation details, applying the correct milestone, project, labels, and issue type for accurate changelog generation and release notes.

Do I need gh CLI authentication to generate issues from pull requests?▼

Yes, generating issues from pull requests requires gh CLI authentication and specific permissions to create issues, ensuring the workflow can map PR metadata and link the PR to the newly created issue.

How does PR to issue mapping handle implementation details and user-visible changes?▼

PR to issue mapping separates WHAT user-visible changes occurred from HOW they were implemented, keeping internal details within the PR while the generated issue tracks only the user-facing problem or feature for release notes.

Can I auto-assign milestones and labels when creating issues from PR metadata?▼

Yes, you can auto-assign milestones, projects, labels, and issue types when creating issues by mapping existing PR metadata and repository conventions directly to the newly generated tracking issue.

What is the best way to track user-visible changes across multiple repositories during PR reviews?▼

The best way to track user-visible changes across repositories is generating standardized tracking issues from PRs, which isolates user-facing features from implementation details and links them to milestones for consistent release notes.

Related Skills

Explore More Software Engineering Skills→
devs6186devs6186

github-workflow-automation

Automates GitHub workflow management with GitHub Actions and gh CLI for CI, PR, and release tasks.

Community
Intermediate
hiddink-aihiddink-ai
1

hiddink-harness-release-notes

Generate structured release notes and update CHANGELOG.md from git commits and closed GitHub issues.

Official
Advanced
blake-goodwynblake-goodwyn

pr-review

Automate pull request code review with confidence-scored issues.

Community
Advanced
vikisingh23vikisingh23
4

changelog

...

Community
Intermediate