repo-standardizer

Standardize GitHub repository labels, issue forms, CI workflows, rulesets, and documentation templates.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill repo-standardizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-standardizer
Source: https://github.com/github/awesome-copilot/tree/main/skills/repo-standardizer
Command: npx skills add https://github.com/github/awesome-copilot --skill repo-standardizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New or neglected GitHub repositories often lack consistent labels, issue templates, CI pipelines, branch protection, and community docs, forcing maintainers to configure each piece manually through the GitHub UI.

Core Features & Use Cases

  • Label taxonomy design: Creates themed rating tiers, P0–P3 priority, impact severity, and status labels via idempotent upsert through the GitHub API.
  • Repository scaffolding: Adds issue forms, PR templates, CI workflows (Node, Python, Go, Rust), CODEOWNERS, rulesets, and docs like README, CONTRIBUTING, and SECURITY from templates.
  • Use Case: After creating a new open-source project, run this Skill to audit the repo, then apply a complete governance setup — labels, branch protection rulesets, CI, and multilingual README files — in one idempotent pass.

Quick Start

Ask the agent to standardize my GitHub repository OWNER/REPO with labels, issue templates, CI, and branch protection.

Frequently Asked Questions about repo-standardizer

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

FAQPage Schema
How do I standardize a GitHub repository's labels and templates?

Run this Skill against the target repo after authenticating the gh CLI. It audits the current state, shows a dry-run plan, then applies labels, issue forms, PR templates, CI workflows, rulesets, and docs idempotently.

How to create GitHub labels in bulk with the gh CLI?

The Skill upserts labels from a labels.json file by checking existence with GET /labels/{name}, then creating with POST or updating with PATCH. Label names are URL-encoded to handle spaces and slashes safely.

Does this tool modify my repository's source code?

No. It only touches repository metadata and configuration files such as .github templates, workflows, labels, rulesets, and documentation. Application code logic is never modified.

What permissions are needed to push CI workflows to GitHub?

The token needs repo scope plus the workflow scope to push workflow files; a 403 on push means the workflow scope is missing. Organization repositories additionally require org membership or admin rights.

Is it safe to run the standardization twice on the same repo?

Yes. Every module is idempotent: labels are upserted, rulesets are fully replaced by name, and existing files are diffed before overwriting. Re-running fills gaps without duplicating or clobbering customized content.

Which CI workflows can be generated for my project?

The Skill detects the stack from package.json, pyproject.toml, go.mod, or Cargo.toml and installs a matching CI template for Node, Python, Go, or Rust. Node workflows handle npm, pnpm, and yarn lockfiles automatically.