skills.rest
Alountk
AlountkCOMMUNITY
Explore all skills by this author →
GitHub

issue-creation

Create and triage GitHub issues using repository-discovered templates, labels, and privacy sanitization.

Updated Aug 5, 2026
Search Tags:#templates#github#bug report#gh cli#triage#privacy#issue creation
One-click install
npx skills add https://github.com/Alountk/Bloodbowl_Project --skill issue-creation-alountk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/Alountk/Bloodbowl_Project/tree/main/.opencode/skills/issue-creation
Command: npx skills add https://github.com/Alountk/Bloodbowl_Project --skill issue-creation-alountk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating GitHub issues without knowing a repository's contribution policy leads to duplicates, wrong templates, invented labels, and leaked private data. This Skill discovers the repository's actual issue workflow before publishing anything. ## Core Features & Use Cases - Repository Policy Discovery: Runs read-only checks with the GitHub CLI to detect issue templates, labels, blank-issue settings, and Discussions support before drafting. - Duplicate Detection and Triage: Searches open and closed issues to comment on existing reports instead of creating duplicates, and verifies triage criteria before approving or closing. - Privacy Sanitization: Replaces usernames, hostnames, tokens, and internal paths with placeholders in every issue body before submission. - Use Case: A user hits a bug in a CLI tool and asks for an issue to be filed; the Skill inspects the repo's issue templates, fills the matching Markdown template from known evidence, sanitizes the reproduction steps, and publishes with only permitted labels. ## Quick Start Ask the assistant to create a GitHub issue in the current repository describing your bug or feature request, and let it discover the repository's templates and labels first.

Frequently Asked Questions about issue-creation

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

FAQPage Schema
How do I create a GitHub issue that follows a repository's template?▼

Discover the repository's issue templates first by listing files under .github/ISSUE_TEMPLATE with git ls-files or the gh CLI. Fill the matching Markdown template from known evidence, then publish with gh issue create using a reviewed body file.

How do I avoid creating duplicate GitHub issues?▼

Search open and closed issues with gh issue list --state all --search before creating anything. If an existing issue covers the same behavior, comment there instead of opening a duplicate.

Can I apply labels when creating a GitHub issue?▼

Only apply labels that actually exist in the repository and that contribution guidance permits you to set. Fetch the label list via the GitHub API and never invent status or priority labels that are not documented.

What should I do when a repository has no issue templates?▼

A no-template fallback is allowed only when blank issues are explicitly enabled on the repository. Otherwise follow the repository's documented contact links or stop and ask rather than publishing an unstructured issue.

How do I avoid leaking private data in GitHub issue reports?▼

Scan the issue body before submission and replace usernames, hostnames, home paths, tokens, and internal ports with explicit placeholders. Keep the reproduction steps runnable by using placeholders like <user> and <token> instead of deleting content.

When should a question go to GitHub Discussions instead of an issue?▼

Use Discussions only when the repository has Discussions enabled and its contribution guidance routes questions there. Otherwise follow the documented support or contact links rather than filing a question as an issue.

Related Skills

Explore More Software Engineering Skills→
dropseeddropseed
1.0k

plain-bug

Collect bug details and create a GitHub issue via gh CLI.

Official
Intermediate
az0512124155azz-sysaz0512124155azz-sys

validate-ui-scenario

Drives a real VS Code window through scripted scenarios and captures video, screenshots, and trace evidence.

Community
Advanced
nielsmadannielsmadan
1

review-history

Analyze Git history to identify code changes and regressions.

Community
Intermediate
arozumenkoarozumenko
18

gathering-context

Gather cross-channel context about a person or topic from email and Teams.

Community
Intermediate