github-repo-hygienelisted

# GitHub Repo Hygiene ## Why this exists Someone deciding whether to hire or trust a developer usually starts with their GitHub. A repo with no description, no topics, and a README that still says "This project was bootstrapped with create-next-app" reads as abandoned or thrown together, even if the code behind it is genuinely good. Most of the time nobody did this on purpose — it's just the stuff that's easy to forget once the code works. This skill closes that gap: find what's missing, then write it. ## Step 1: Figure out the scope Ask (or infer from context) whether this is: - One specific repo (`owner/repo`) - Every repo under one GitHub account/org - A specific handful of repos Don't assume "audit everything" if the user only mentioned one project — but if they say something like "clean up my GitHub" with no repo named, default to auditing all of their non-fork repos. ## Step 2: Run the audit script ```bash bash scripts/audit_repos.sh <owner> # every repo bash scripts/audit_repos.sh <owner>/<repo> [owner/repo2] # specific repos ``` This is read-only — it never changes anything, it just reports. It prints one JSON object per line with `issues` (a list of what's wrong) and `clean` (true if nothing was found). Requires `gh auth status` to already be logged in; if it's not, tell the user to run `gh auth login` first rather than trying to authenticate on their behalf. A repo can look clean by this script's checks and still be worth a second look