Help us improve
Share bugs, ideas, or general feedback.
From slim-rebranding
Adds standardized GitHub issue templates for bug reports and feature requests, supporting both Markdown and GitHub Form formats.
npx claudepluginhub nasa-ammos/slim --plugin slim-changelogHow this skill is triggered — by the user, by Claude, or both
Slash command
/slim-rebranding:slim-issue-templatesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Helps development teams keep the language of bug reports, feature requests, and other types of issues readable and consistent. This skill provides both traditional Markdown templates and modern GitHub Form templates.
Generates GitHub YAML issue templates for bug reports and feature requests in .github/ISSUE_TEMPLATE/. Includes structured fields, auto-labels, and optional config.yml to standardize maintainer info intake.
Manages full GitHub issue lifecycle: create with conventional commit titles, sub-issues, cross-repo links, edit/view/list, dump trees to markdown/YAML, push from files, comment/label/close.
Helps with drupal.org issue templates, formatting, contributing patches, and best practices. Guides users through creating issues, creating merge requests, and submitting fixes back to drupal.org projects.
Share bugs, ideas, or general feedback.
Helps development teams keep the language of bug reports, feature requests, and other types of issues readable and consistent. This skill provides both traditional Markdown templates and modern GitHub Form templates.
bug_report.md): Traditional freeform template with guidancebug_report.yml): Structured form with required fieldsnew_feature.md): Freeform template for feature proposalsnew_feature.yml): Structured form for feature requestsCheck if issue templates already exist:
ls -la .github/ISSUE_TEMPLATE/
If templates exist, ask the user if they want to replace them or keep them.
Ask the user which format they prefer:
Recommendation: GitHub Forms (.yml) provide better structure and validation, reducing incomplete reports.
Create the .github/ISSUE_TEMPLATE/ directory if it doesn't exist:
mkdir -p .github/ISSUE_TEMPLATE
Based on the user's choice, copy the appropriate templates:
For Markdown templates:
cp assets/bug_report.md .github/ISSUE_TEMPLATE/
cp assets/new_feature.md .github/ISSUE_TEMPLATE/
For GitHub Forms:
cp assets/bug_report.yml .github/ISSUE_TEMPLATE/
cp assets/new_feature.yml .github/ISSUE_TEMPLATE/
For both:
cp assets/*.md .github/ISSUE_TEMPLATE/
cp assets/*.yml .github/ISSUE_TEMPLATE/
The templates can be customized to fit the project:
Advantages:
Disadvantages:
Advantages:
Disadvantages:
Edit the .md files to:
Edit the .yml files to:
Example field types:
- type: input # Single-line text
- type: textarea # Multi-line text
- type: dropdown # Select from options
- type: checkboxes # Multiple selection
bug_report.md: Markdown bug report templatebug_report.yml: GitHub Form bug report templatenew_feature.md: Markdown feature request templatenew_feature.yml: GitHub Form feature request template