create-github-issue_skill

This skill creates GitHub issues using gh with repository templates, automatically filling fields, labels, assignees, milestones, and draft options.

Rust

4.6k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill antinomyhq/forge --skill create-github-issue

SKILL.md4.0 KB

Overview

This skill creates GitHub issues using the gh CLI while automatically discovering and following the repository's official issue templates. It supports templates, required fields, labels from .github/labels.json, assignees, milestones, and draft issues to produce clean, valid issues ready to open.

How this skill works

The skill first inspects .github/ISSUE_TEMPLATE/ to list and read available YAML templates, then maps each template field into a matching Markdown section. It inspects .github/labels.json to pick only allowed labels and gathers local repo context (git status, recent commits, related issues) when helpful. Finally it writes the composed body to .forge/FORGE_ISSUE_BODY.md and runs gh issue create with the appropriate flags, returning the created issue URL and a short summary.

When to use it

User asks to create a GitHub issue, bug report, or feature request.
Open an RFC, proposal, or research draft in a repository.
User supplies logs, stack traces, or reproduction steps to file an accurate bug.
You need consistent issues that match the repo’s required metadata and labels.

Best practices

Always discover templates in .github/ISSUE_TEMPLATE/ and read the selected YAML—never assume structure.
Populate every field marked required in the template; do not leave placeholder text.
Only use labels present in .github/labels.json and include a type: label for the issue kind.
Keep titles under 70 characters, imperative, and follow any template prefix.
Place logs and configs in proper fenced code blocks per the template render guidance.

Example use cases

File a bug using the repo’s bug_report.yml template with Steps to Reproduce, Expected/Actual behavior, and logs.
Submit a feature request using feature_request.yml, including motivation, proposal, and acceptance criteria.
Open a research or proposal as a draft issue with --draft and a milestone or assignee if requested.
Create an issue that links to recent commits and related issues discovered via gh issue list and git log.

FAQ

No. It only reads templates and labels from .github and uses them to format the issue; it never modifies repository config files.

What if the repository has multiple templates that seem applicable?

The skill selects the most appropriate template based on the requested issue type and template content; it will prefer explicit bug/feature templates when present.

Can I provide logs or code to be included?

Yes. Provide those items and they will be inserted into the exact template sections required, using fenced code blocks when the template requests them.