slim-issue-templates

Generates GitHub issue templates for bugs and feature requests in Markdown and Form formats.

35|14|Updated Feb 16, 2022

Search Tags:#automation #templates #GitHub #feature-request #bug-report #issue-templates

Ready to run

npx skills add https://github.com/NASA-AMMOS/slim --skill slim-issue-templates

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slim-issue-templates
Source: https://github.com/NASA-AMMOS/slim/tree/main/static/marketplace/skills/slim-issue-templates
Command: npx skills add https://github.com/NASA-AMMOS/slim --skill slim-issue-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill provides ready-to-use GitHub issue templates for bugs and feature requests, helping teams enforce consistent reporting and reduce noise.

Core Features & Use Cases

Markdown templates for bug reports and feature requests, usable in any repository.
GitHub Form templates (YAML) for structured issue submission.
Use case: When starting a new project, copy the templates into .github/ISSUE_TEMPLATE to standardize initial issue reporting and onboarding.

Quick Start

Place the templates into your repository's .github/ISSUE_TEMPLATE directory and enable them. For Markdown templates, copy assets/bug_report.md and assets/new_feature.md to .github/ISSUE_TEMPLATE/. For GitHub Forms, copy assets/bug_report.yml and assets/new_feature.yml to .github/ISSUE_TEMPLATE/. Then commit and push; in GitHub, go to Issues to see the new templates.

Frequently Asked Questions about slim-issue-templates

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

FAQPage Schema

How do I standardize GitHub issues with ready templates for bug reports and feature requests?▼

To standardize GitHub issues, you copy ready-to-use Markdown or YAML form templates into your repository's .github/ISSUE_TEMPLATE directory. This enforces consistent issue reporting and reduces noise by providing structured formats for bug reports and feature requests.

What is the difference between Markdown and GitHub Form templates for issue reporting?▼

Markdown templates provide standard text-based issue forms, while GitHub Form templates use YAML to create structured, fill-in-the-blank submission fields. Both formats populate the .github/ISSUE_TEMPLATE directory to standardize how users submit bug reports and feature requests.

How do I set up GitHub issue templates in my repository?▼

To set up GitHub issue templates, copy the bug_report and new_feature template files from the assets directory into your repository's .github/ISSUE_TEMPLATE folder. Commit and push the changes, then navigate to the Issues tab in GitHub to see the new templates enabled.

Can I use these issue templates in any GitHub repository?▼

Yes, you can use these Markdown and YAML issue templates in any GitHub repository. The templates are ready-to-use and can be applied to standardize initial issue reporting and onboarding for new projects by simply copying them into the correct directory.

Do I need any dependencies or special tools to use GitHub issue templates?▼

No dependencies or special tools are required to use these GitHub issue templates. You simply need a GitHub repository where you can place the Markdown and YAML files into the .github/ISSUE_TEMPLATE directory to enable automatic integration and standardize issue reporting.