Agent skill · github
repo-standardizer
Polish any GitHub repository's surface — labels (emoji rating tiers, P0–P3 priority, impact severity), issue forms, PR template, CI workflows, CODEOWNERS, rulesets, docs. Repo meta & config only — no code logic touched. Use when creating a new repo or polishing an existing one.
What it needs
About 12k tokens when loaded.
What this skill does
GitHub Repo Standardizer Detect a repository's current state, then polish its surface: issue forms, PR template, label taxonomy, CI, CODEOWNERS, rulesets, docs. Works on repo metadata and config files only — code logic is never touched. Idempotent — safe to re-run; fills gaps and reconciles drift without duplicating or clobbering. When to use User says "standardize / tidy up / professionalize this repo" A new repo was just created and needs templates, labels, CI, and rules from day one A repo looks bare: no templates, no labels, no CI, no branch protection Preflight (mandatory, in order) Requires: gh CLI (authenticated), git, jq, python3 — verify they exist before starting (which gh git jq python3). 1. Authenticate — check gh login first Logged in → continue; print gh api user -q .login so the user knows which account will act. Not logged in → STOP. Tell the user (do not guess): 1. Run gh auth login (web/device flow), or 2. Export a token: export GHTOKEN=ghpxxx — needs repo, workflow (for CI files) and, for org repos, admin:org (or admin:repohook / org membership admin) scopes. Never paste tokens into chat, logs, or files. If the user pastes a token in chat, advise them to revoke it and re-issue. If gh auth login is impossible in this environment (headless), suggest gh auth login --with-token reading from a file the user created. Verify the acting account can write to the target: admin/member → OK. 404 → stop and ask the user to add the account to the org first. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/repo-standardizer