gh_issue_create

Create GitHub issues from summaries using standardized templates.

1|Updated Oct 19, 2025

Search Tags:#automation #workflow #templates #github #cli #issue #generate

Ready to run

npx skills add https://github.com/acartine/osterman --skill gh-issue-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh_issue_create
Source: https://github.com/acartine/osterman/tree/main/skills/gh_issue_create
Command: npx skills add https://github.com/acartine/osterman --skill gh-issue-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating GitHub issues from summaries or notes is error-prone and inconsistent; this skill standardizes formatting and templates to speed up triage and ensure complete context.

Core Features & Use Cases

Template-driven creation for bugs, features, docs, tests, and refactors to guarantee necessary sections are included.
Type-based generation: specify issue type and optional target repo to generate a ready-to-submit issue body.
Use Case: turn meeting notes or triage discussions into consistent GitHub issues that teammates can act on immediately.

Quick Start

Create a new issue by specifying the type and description.

Frequently Asked Questions about gh_issue_create

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

FAQPage Schema

How do I create GitHub issues with consistent templates from meeting notes?▼

You can create GitHub issues with consistent templates by specifying the issue type and an optional target repository. This generates a ready-to-submit issue body that standardizes formatting and ensures complete context for team triage.

What issue types are supported by automated GitHub issue generation?▼

Automated GitHub issue generation supports template-driven creation for bugs, features, docs, tests, and refactors. Type-based validation guarantees necessary sections are included to speed up triage and project visibility.

Can I specify a target repository when generating a GitHub issue?▼

Yes, you can specify an optional target repository when generating a GitHub issue. The workflow validates the issue type, applies the correct template, and returns the created issue URL for the specified repository.

What is the best way to standardize GitHub issue formatting for engineering workflows?▼

The best way to standardize GitHub issue formatting is using template-driven generation with type validation. This approach transforms inconsistent notes or triage discussions into structured issues, improving project visibility and triage speed.

Why does creating GitHub issues manually from notes lead to triage problems?▼

Creating GitHub issues manually from notes is error-prone and inconsistent, which slows down triage. Standardized templates solve this by guaranteeing necessary sections are included, ensuring teammates have complete context to act immediately.