github-issue-form-templates

Create and manage GitHub issue form templates in YAML across repositories.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/prulloac/git-blame-vsc --skill github-issue-form-templates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-form-templates
Source: https://github.com/prulloac/git-blame-vsc/tree/main/.agents/skills/github-issue-form-templates
Command: npx skills add https://github.com/prulloac/git-blame-vsc --skill github-issue-form-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

YAML-based GitHub issue templates enable teams to standardize data collection, guide contributors, and reduce ambiguity by codifying form schemas that enforce structure and validations.

Core Features & Use Cases

  • Create, customize, and publish GitHub issue forms using YAML syntax across repositories
  • Define field types (input, textarea, dropdown, checkboxes, markdown, hidden) with validations and defaults
  • Attach reusable references and assets to support guidance, examples, and templates
  • Use for bug reports, feature requests, security disclosures, and governance issues

Quick Start

Place a complete YAML form under .github/ISSUE_TEMPLATE and commit it to enable the template.

Frequently Asked Questions about github-issue-form-templates

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

FAQPage Schema
How do I create GitHub issue form templates using YAML?

Create GitHub issue form templates by defining a YAML file with required frontmatter (name and description) and a body section describing form fields, then place it under the .github/ISSUE_TEMPLATE directory in your repository.

What field types are supported in GitHub YAML issue forms?

GitHub YAML issue forms support input, textarea, dropdown, checkboxes, markdown, and hidden field types. Fields can include validations, default values, and attributes like labels and descriptions.

Can I use GitHub issue forms for security disclosures and bug reports?

Yes, GitHub issue forms can standardize data collection for bug reports, feature requests, security disclosures, and governance issues by enforcing structured schemas with validations across repositories.

What's the best way to standardize issue data collection across multiple GitHub repositories?

Standardize issue data collection by applying reusable YAML issue form templates across repositories. Define field schemas with validations and defaults, attach guidance assets, and commit the YAML files to each repository's .github/ISSUE_TEMPLATE folder.

Does a GitHub YAML issue form template require frontmatter?

Yes, GitHub YAML issue form templates enforce a frontmatter section that must include a name and description. The body section describes the actual form fields and structure that contributors will see.

Can I attach reference materials to GitHub issue form templates?

Yes, GitHub issue form templates support optional references and assets components that provide contributors with guidance, examples, and supporting documentation directly within the issue creation workflow.