github-repolisted

# GitHub Repository Optimizer This skill audits a GitHub repository against best practices and generates or improves the files that make a repo look professional, welcoming, and well-maintained. It works with live repos (via `gh` CLI), local git directories, or files the user provides. ## Workflow 1. **Gather repo context** — Determine what we're working with and collect information 2. **Run the audit** — Score every aspect of the repo's public-facing quality 3. **Generate or improve files** — Produce the files that are missing or need work 4. **Verify** — Confirm the outputs are correct and complete --- ## Phase 0: Gather Context Figure out what you're working with. Try these sources in order: ### If in a local git directory Check the current working directory for a `.git` folder. If present: - Read the existing README.md, CONTRIBUTING.md, SECURITY.md, CODE_OF_CONDUCT.md, LICENSE, CHANGELOG.md - Check `.github/` for issue templates, PR templates, workflows, CODEOWNERS, FUNDING.yml, dependabot.yml - Run `git remote -v` to identify the GitHub remote - Run `git branch -a` to assess branch hygiene - Run `git tag --list` to check release tagging ### If `gh` CLI is available and authenticated Try `gh auth status` first. If authenticated: - `gh repo view --json name,description,url,homepageUrl,repositoryTopics,licenseInfo,isArchived,defaultBranchRef,stargazerCount,forkCount,hasIssuesEnabled,hasWikiEnabled` — repo metadata - `gh api repos/{owner}/{repo}/community/profile