github

Configure GitHub repositories with standard labels, templates, workflows, and branch protections.

Updated Mar 28, 2026

Search Tags:#templates #github #workflows #labels #project-board #branch-protection

Ready to run

npx skills add https://github.com/rodacato/kwik-e-dev --skill github-rodacato

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github
Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/launchpad/skills/github
Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill github-rodacato

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Configures GitHub repositories with rodacato-standard labels, issue/PR templates, workflows, project boards, merge strategies, and branch protections to enforce consistent collaboration practices.

Core Features & Use Cases

Create and enforce standard labels (feature, bug, agent:active, agent:review, etc.) and issue templates.
Provide PR templates and workflow automation to enforce linking PRs to issues, squash merge strategy, and project board automation.
Scaffold GitHub configuration for new repos or repos missing standard templates and protections.
Optional project board setup and branch protection on main to harden workflows.

Quick Start

Follow the included setup steps to apply standard labels, templates, workflows, and protection rules to your repository.

Frequently Asked Questions about github

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

FAQPage Schema

How do I set up GitHub branch protection and standard labels for a new repository?▼

You can enforce GitHub PR templates and workflows by applying rodacato-standard templates that require linking pull requests to issues, enforcing a squash merge strategy, and automating project board updates.

Can I apply standard issue templates and workflows to an existing GitHub repository?▼

Yes, you can apply standard issue templates and workflows to an existing GitHub repository if it is missing standard labels, templates, or merge protections, bringing it to a fully automated setup state.

What is the best way to automate project board setup and enforce merge rules in GitHub?▼

To configure squash merge and mandatory issue linkage, you apply workflow automation templates that enforce the squash merge strategy and require pull requests to link directly to existing issues before merging.

Does this GitHub configuration process require existing repository labels?▼

No, this GitHub configuration process does not require existing labels; it creates and enforces standard labels like feature, bug, agent:active, and agent:review on both brand-new and existing repositories.

Why should I use a standardized GitHub bootstrap process instead of manual repository setup?▼

You should use a standardized GitHub bootstrap process to eliminate manual setup errors, ensure consistent collaboration practices across multiple repositories, and harden workflows with automated branch protection and template enforcement.