creating-issue

Create validated GitHub issues with structured templates and gh CLI labels.

168|55|Updated Jun 3, 2025
One-click install
npx skills add https://github.com/tile-ai/TileOPs --skill creating-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-issue
Source: https://github.com/tile-ai/TileOPs/tree/main/.claude/skills/creating-issue
Command: npx skills add https://github.com/tile-ai/TileOPs --skill creating-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent, incomplete, or improperly labeled GitHub issues slow down triage and block high-quality collaboration in TileOPs. This Skill standardizes issue titles, bodies, plans, constraints, and acceptance criteria so maintainers and contributors have clear, actionable reports.

Core Features & Use Cases

  • Structured Issue Assembly: Extracts arguments, builds a canonical title, and assembles a descriptive issue body with symptom, root cause analysis, related files, goal, plan, constraints, and acceptance criteria.
  • Validation & Hard Gates: Enforces required sections and non-empty fields before creating issues to prevent incomplete filings.
  • Labeling Integration: Looks up TYPE-to-label mappings in .claude/conventions/types.sh and applies appropriate labels using the GitHub CLI.
  • Use Case: A contributor detects a performance regression in the GEMV kernel and uses this Skill to generate a validated PERF[GEMV] issue with a clear plan and acceptance criteria for reviewers.

Quick Start

Use the creating-issue skill to draft and file a PERF/GEMV issue with a validated title, detailed root cause analysis, a proposed plan, and acceptance criteria.

Frequently Asked Questions about creating-issue

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

FAQPage Schema
How do I create GitHub issues with structured templates using gh CLI?

To create GitHub issues with structured templates, this Skill parses your arguments and enforces canonical titles and descriptive bodies with symptom, root cause, plan, and acceptance criteria using the gh CLI.

What is the best way to automate GitHub issue labeling and validation?

Automating GitHub issue labeling and validation requires enforcing non-empty fields and mapping TYPE categories to labels. This Skill references .claude/conventions/types.sh to look up and apply labels automatically.

How do I file a PERF or BUG issue that passes triage hard gates?

Filing a PERF or BUG issue that passes triage hard gates requires structured sections like root cause analysis and acceptance criteria. This Skill validates required fields and prevents incomplete filings before running gh commands.

Can I use standard GitHub issue templates for FEAT and REFACTOR reports?

Standard GitHub issue templates for FEAT and REFACTOR reports are fully supported. This Skill assembles validated titles and bodies conforming to TileOPs repository conventions for multiple issue types including DOCS, TEST, and META.

Why does my GitHub issue creation fail validation checks?

GitHub issue creation fails validation checks when required sections are empty or missing. This Skill enforces hard gates on structured template fields like goal, plan, and constraints before executing the gh CLI commands.

Does the creating-issue Skill work without external dependencies?

The creating-issue Skill works without external dependencies. It relies solely on the gh CLI and internal repository convention files to parse arguments, validate templates, and apply labels for high-quality issue filing.