playbooks

home / skills / ehtbanton / claudeskillsrepo / issue-template-generator

issue-template-generator skill

/issue-template-generator

This skill generates complete GitHub issue templates for bugs, features, and questions in YAML form for immediate use.

npx playbooks add skill ehtbanton/claudeskillsrepo --skill issue-template-generator

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
710 B
---
name: issue-template-generator
description: Generate GitHub issue templates for bug reports, feature requests, and questions. Triggers on "create issue template", "generate github issue template", "bug report template", "feature request template".
---

# Issue Template Generator

Generate GitHub issue templates for standardized issue reporting.

## Output Requirements

**File Output:** `.github/ISSUE_TEMPLATE/*.yml`
**Format:** YAML issue forms
**Standards:** GitHub Issue Templates

## When Invoked

Immediately generate complete issue templates for the repository.

## Example Invocations

**Prompt:** "Create GitHub issue templates"
**Output:** Complete templates for bugs, features, and questions.

Overview

This skill generates ready-to-use GitHub issue templates for bug reports, feature requests, and questions. It outputs YAML issue forms placed under .github/ISSUE_TEMPLATE to enforce consistent, structured issue submission. Templates follow GitHub Issue Templates standards and are immediately usable in the repository.

How this skill works

When triggered, the skill composes three complete YAML issue form files (bug_report.yml, feature_request.yml, question.yml) with fields, labels, and suggested reviewers. Each template includes title, body fields, required checkboxes, and metadata such as labels and issue type to streamline triage. The skill returns the full file contents so you can paste them directly into .github/ISSUE_TEMPLATE.

When to use it

  • You want consistent, structured bug reports from contributors.
  • You need a clear template for feature requests to capture motivation and acceptance criteria.
  • You want to reduce back-and-forth by collecting reproductions and environment details up front.
  • You are initializing a repository and want ready-to-use issue forms.
  • You need templates that integrate with labels and triage workflows.

Best practices

  • Require a minimal set of fields (summary, steps to reproduce, expected vs actual) for bugs to improve reproducibility.
  • Include optional checkboxes for common items (e.g., 'I searched existing issues') to reduce duplicates.
  • Add suggested labels and assignees in metadata to speed triage and routing.
  • Keep fields concise and use examples to show how to fill them out.
  • Review and iterate templates based on contributor feedback and triage pain points.

Example use cases

  • Create a bug_report.yml that collects environment, steps, logs, and a reproducible example.
  • Generate a feature_request.yml that asks for problem statement, proposed solution, and acceptance criteria.
  • Produce a question.yml to direct support requests with required context and version info.
  • Add metadata labels like 'bug', 'feature', or 'support' to automate workflows.
  • Bootstrap issue templates for a new TypeScript project to reduce noise during early development.

FAQ

What file names and paths are produced?

The skill generates YAML files intended for .github/ISSUE_TEMPLATE, typically named bug_report.yml, feature_request.yml, and question.yml.

Can the templates include required fields and labels?

Yes. Each YAML form can define required fields, checkboxes, placeholders, and metadata such as labels and assignees to support repository workflows.