repo-standardizerlisted
Install: claude install-skill programmingWTF/repo-standardizer
# 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)
### 1. Authenticate — check gh login first
```bash
gh auth status 2>/dev/null || echo "NOT_LOGGED_IN"
```
- **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 GH_TOKEN=ghp_xxx` — needs `repo`, `workflow` (for CI files) and, for org repos, `admin:org` (or `admin:repo_hook` / 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:
```bash
# user repos: no extra check needed beyond token scopes
# or