issue-pr-templates

Builds the structured intake layer that turns "it's broken, please fix" into actionable reports. The failure this skill fixes: models write legacy Markdown issue templates (no required fields), get the YAML forms schema subtly wrong (forms silently don't render), and forget config.yml routing entirely.

When NOT to use

• CONTRIBUTING/SECURITY/SUPPORT prose files → community-health.
• Triaging or closing existing issues, stale-bot automation → out of scope.
• Requiring PR reviews/checks before merge → repo-protections.
• Configuring GitHub Discussions itself → out of scope (linking to it is in scope).

Workflow