create-github-issue

Generate GitHub issue templates with Summary, Scope, Acceptance Criteria, Dependencies, and Notes.

1|1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/hyperjumptech/mediapulse --skill create-github-issue-hyperjumptech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-github-issue
Source: https://github.com/hyperjumptech/mediapulse/tree/main/.cursor/skills/create-github-issue
Command: npx skills add https://github.com/hyperjumptech/mediapulse --skill create-github-issue-hyperjumptech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structures GitHub issue titles and markdown bodies (Summary, Scope, Acceptance criteria, Dependencies, Notes) and creates issues with gh using --body-file and temp files outside the repo. Use when creating or drafting a GitHub issue, running gh issue create, filing a ticket before a PR, or when the user asks for issue format or templates.

Core Features & Use Cases

  • Templates for a consistent issue structure with a Summary, Scope, Acceptance Criteria, Dependencies, and Notes.
  • Generates a body file suitable for gh issue create using --body-file to avoid committing the issue content.
  • Works across workflows to draft or file issues before PRs, or when users request predefined issue templates.

Quick Start

Draft a well-structured GitHub issue with a Summary, Scope, Acceptance Criteria, and Dependencies, then create the issue using gh with a body-file.

Frequently Asked Questions about create-github-issue

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

FAQPage Schema
How do I create a structured GitHub issue using the command line?

To create a structured GitHub issue using the command line, generate a markdown body file with Summary, Scope, Acceptance Criteria, Dependencies, and Notes sections, then run the gh issue create command using the --body-file flag.

What sections should be included in a GitHub issue template?

A GitHub issue template should include sections for Summary, Scope, Acceptance Criteria, Dependencies, and Notes to standardize ticket creation and clearly define the problem scope and expected outcomes.

Can I draft a GitHub issue without committing the content to my repository?

Yes, you can draft a GitHub issue without committing content by generating a temporary body file outside the repository and passing it to the gh issue create command via the --body-file flag.

Does gh issue create work with a predefined markdown body-file?

Yes, the gh issue create command works with a predefined markdown body-file by using the --body-file flag, allowing you to apply structured templates while avoiding manual text entry in the terminal.

When should I file a GitHub ticket before submitting a pull request?

You should file a GitHub ticket before submitting a pull request to establish a structured record of the changes, ensuring the Summary, Scope, and Acceptance Criteria are documented for review.

What is the best way to standardize GitHub issues across different workflows?

The best way to standardize GitHub issues across workflows is to use predefined templates that enforce consistent sections like Dependencies and Notes, paired with automated gh issue creation via body-files.