create-github-pull-request-from-specification

github/awesome-copilot · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/github/awesome-copilot --skill create-github-pull-request-from-specification
0 commentsdiscussion
summary

Automated GitHub pull request creation from specification templates with draft-to-review workflow.

  • Reads pull request template from .github/pull_request_template.md and extracts requirements to populate PR body and title
  • Checks for existing pull requests on the target branch before creation to prevent duplicates
  • Progresses pull requests from draft status to ready for review, then auto-assigns to the creator
  • Analyzes PR diffs to ensure specification changes are properly documented
skill.md

Create GitHub Pull Request from Specification

Create GitHub Pull Request for the specification at ${workspaceFolder}/.github/pull_request_template.md .

Process

  1. Analyze specification file template from '${workspaceFolder}/.github/pull_request_template.md' to extract requirements by 'search' tool.
  2. Create pull request draft template by using 'create_pull_request' tool on to ${input:targetBranch}. and make sure don't have any pull request of current branch was exist get_pull_request. If has continue to step 4, and skip step 3.
  3. Get changes in pull request by using 'get_pull_request_diff' tool to analyze information that was changed in pull Request.
  4. Update the pull request body and title created in the previous step using the 'update_pull_request' tool. Incorporate the information from the template obtained in the first step to update the body and title as needed.
  5. Switch from draft to ready for review by using 'update_pull_request' tool. To update state of pull request.
  6. Using 'get_me' to get username of person was created pull request and assign to update_issue tool. To assign pull request
  7. Response URL Pull request was create to user.

Requirements

  • Single pull request for the complete specification
  • Clear title/pull_request_template.md identifying the specification
  • Fill enough information into pull_request_template.md
  • Verify against existing pull requests before creation
how to use create-github-pull-request-from-specification

How to use create-github-pull-request-from-specification on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add create-github-pull-request-from-specification
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/github/awesome-copilot --skill create-github-pull-request-from-specification

The skills CLI fetches create-github-pull-request-from-specification from GitHub repository github/awesome-copilot and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/create-github-pull-request-from-specification

Reload or restart Cursor to activate create-github-pull-request-from-specification. Access the skill through slash commands (e.g., /create-github-pull-request-from-specification) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.764 reviews
  • Soo Thompson· Dec 28, 2024

    create-github-pull-request-from-specification has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Isabella Harris· Dec 24, 2024

    We added create-github-pull-request-from-specification from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Diego Jackson· Dec 24, 2024

    Keeps context tight: create-github-pull-request-from-specification is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Dhruvi Jain· Dec 12, 2024

    create-github-pull-request-from-specification is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ava Martinez· Dec 4, 2024

    Keeps context tight: create-github-pull-request-from-specification is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Arjun Jain· Nov 23, 2024

    create-github-pull-request-from-specification is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Omar Jackson· Nov 19, 2024

    Useful defaults in create-github-pull-request-from-specification — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Omar White· Nov 15, 2024

    create-github-pull-request-from-specification fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Noah Bhatia· Nov 15, 2024

    create-github-pull-request-from-specification is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Oshnikdeep· Nov 3, 2024

    Keeps context tight: create-github-pull-request-from-specification is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 64

1 / 7