repolishlisted

# repolish A command-line tool that scores 22 concrete signals about a repository and, for every point it deducts, names the file and line and says what to write instead. **No model is in the scoring path.** The same commit always produces the same score. You may suggest wording; you must never claim a number the tool did not produce. ## The rule that matters most **Do not rewrite the README.** Your instinct will be to replace it with a well-structured one. That destroys the author's voice, their layout, their examples, and usually their accuracy. Instead: 1. **Measure.** `repolish` — one command. It scores the repository and prints every file it would touch, and it writes **nothing**. 2. **Show the user that plan, then apply it.** `repolish --apply` — badge, table of contents, issue/PR templates, `CONTRIBUTING.md`, the CI workflow. It only ever *inserts*; the diff is new lines and nothing else. 3. **Hand back what needs judgement.** A missing quickstart, a vague tagline, a README claim whose command no longer exists — those need the author's knowledge, or a targeted edit you can justify from evidence. 4. **Measure again** and report the delta — `repolish --stages check --base <ref>` does the arithmetic for you and lists only the checks that moved. Only edit prose directly when a finding names a specific line and the fix is unambiguous, and say which finding you were acting on. ## Install **Check first, then install.** Every command below calls `repo