issue-creation

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

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill issue-creation-carloswilliamsr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-creation
Source: https://github.com/CarlosWilliamsR/SketchOS/tree/main/.config/opencode/skills/issue-creation
Command: npx skills add https://github.com/CarlosWilliamsR/SketchOS --skill issue-creation-carloswilliamsr

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 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: Searches open and closed issues so you comment on an existing thread instead of filing a duplicate. - Privacy Sanitization: Replaces usernames, hostnames, tokens, and private project names with placeholders before submission. - Use Case: You hit a bug in an open-source CLI tool. The Skill checks the repo's issue templates, finds a matching bug-report form, fills required fields from your evidence, sanitizes your local paths, and publishes the issue with only permitted labels. ## Quick Start Create a GitHub issue in this repository for the bug I just described, following the repository's templates and label policy.

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 under .github/ISSUE_TEMPLATE first, then fill the matching Markdown template from known evidence and publish with gh issue create. For YAML issue forms, open the web issue chooser instead of parsing the schema.

How do I avoid creating duplicate GitHub issues?

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

Can I apply labels when creating a GitHub issue?

Only apply labels returned by repository discovery via the labels API, and only when contribution guidance permits the actor to apply them. Never invent labels or a status taxonomy that the repository does not document.

What should I do if a repository has no issue templates?

A no-template fallback is allowed only when blank issues are explicitly enabled. Otherwise follow the repository's contact links or stop and ask; never publish a fallback issue without that permission.

How do I remove sensitive data from a GitHub issue before submitting?

Replace usernames, hostnames, home paths, tokens, and private project names with explicit placeholders like <user> or <token> before running gh issue create. Keep public tool names and example domains intact so the reproduction stays runnable.