readme-and-co:github-templates

Generate GitHub issue templates, PR templates, and CODEOWNERS configurations.

4|1|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill readme-and-co-github-templates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: readme-and-co:github-templates
Source: https://github.com/aaronbassett/aaronbassett-marketplace/tree/main/plugins/readme-and-co/skills/github-templates
Command: npx skills add https://github.com/aaronbassett/aaronbassett-marketplace --skill readme-and-co-github-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub repositories often struggle with inconsistent issue and pull request templates, CODEOWNERS assignments, and onboarding guidance. This skill provides ready-to-use templates and ownership configurations to standardize contributions across projects.

Core Features & Use Cases

  • Prebuilt issue templates (Markdown and YAML forms) for bugs, feature requests, and questions.
  • Pull request templates and CODEOWNERS guidance to streamline reviews and ownership.
  • Guidance for selecting between Markdown and YAML templates and when to apply each format.

Quick Start

  • Create templates under .github/ISSUE_TEMPLATE and .github/PULL_REQUEST_TEMPLATE
  • Place a CODEOWNERS file at the repository root or .github directory
  • Use this skill to generate or adapt templates for new projects or to standardize existing repos.

Frequently Asked Questions about readme-and-co:github-templates

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

FAQPage Schema
How do I set up GitHub issue templates and PR templates for a new repository?

To set up GitHub templates, create issue templates under .github/ISSUE_TEMPLATE and pull request templates under .github/PULL_REQUEST_TEMPLATE. This skill generates prebuilt Markdown and YAML forms to standardize repository contribution workflows.

What is the difference between Markdown and YAML issue templates on GitHub?

Markdown issue templates provide basic structured forms, while YAML issue templates offer advanced form controls and validations. This skill guides selecting between Markdown and YAML formats based on your repository's specific contribution needs.

Where should I place the CODEOWNERS file in my GitHub repository?

The CODEOWNERS file should be placed at the repository root or within the .github directory. This skill provides CODEOWNERS configurations to automate ownership rules and streamline pull request reviews across projects.

Can I standardize contribution workflows across multiple open-source repositories?

Yes, you can standardize contribution workflows across multiple repositories by applying consistent issue templates, PR templates, and CODEOWNERS rules. This skill adapts ready-to-use configurations for new projects and existing repos.

What GitHub templates do I need for bugs, feature requests, and questions?

You need specific issue templates for bugs, feature requests, and questions to categorize contributions effectively. This skill provides prebuilt templates in both Markdown and YAML forms to cover these standard open-source scenarios.