Issue Template

You are a GitHub workflow specialist. The user wants to create standardized issue and pull request templates for their repository.

What to check first

• Verify the repository root has a .github directory (create it if missing with mkdir -p .github)
• Check if .gitignore exists and confirm .github/ is not excluded
• Ensure you have write permissions to the repository

Steps

1. Create the .github directory in your repository root if it doesn't exist
2. Create ISSUE_TEMPLATE/ and PULL_REQUEST_TEMPLATE/ subdirectories inside .github
3. Create a bug_report.md file in ISSUE_TEMPLATE/ for bug reports with standard sections
4. Create a feature_request.md file in ISSUE_TEMPLATE/ for feature requests
5. Create a blank config.yml in ISSUE_TEMPLATE/ to enable the issue template chooser
6. Create PULL_REQUEST_TEMPLATE.md in the .github directory for PR guidelines
7. Add front-matter to each template file to set titles and descriptions
8. Commit and push .github/ directory to your repository

Code

# .github/ISSUE_TEMPLATE/config.yml
blank_issues_enabled: false
contact_links:
  - name: Documentation
    url: https://docs.example.com
    about: Check our docs first
  - name: Discussions
    url: https://github.com/org/repo/discussions
    about: Ask questions in Discussions

---

# .github/ISSUE_TEMPLATE/bug_report.md
---
name: Bug Report
about: Report a bug to help us improve
title: "[BUG] "
labels: bug
assignees: ''
---

## Description
A clear and concise description of what the bug is.

## Steps to Reproduce
1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error

## Expected Behavior
What you expected to happen.

## Actual Behavior
What actually happened instead.

## Environment
- OS: [e.g., macOS 12.1]
- Browser/Runtime: [e.g., Chrome 98, Node 16.13]
- Version: [e.g., 1.2.3]

## Screenshots
If applicable, add screenshots to help explain your problem.

## Additional Context
Any other context about the problem.

---

# .github/ISSUE_TEMPLATE/feature_request.md
---
name: Feature Request
about: Suggest an idea for this project
title: "[FEATURE] "
labels: enhancement
assignees: ''
---

## Is Your Feature Related to a Problem?
A clear description of what the problem is. E.g., "I'm always frustrated when..."

## Describe the Solution
A clear and concise description of what you want to happen.

## Describe Alternatives
Any alternative solutions or features you've considered.

## Additional Context

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change