repo-description-polishlisted

<!-- Author: jamestexas — drafted by claude-opus-4-7 (2026-05-16) --> # /repo-description-polish — GitHub Repo Description Audit the GitHub repository `description` field and propose a polished replacement. ## Arguments `$ARGUMENTS` - **`<owner/repo>`** — one or more target repos. Defaults to the repo containing the current working directory. - **`--dry-run`** *(default)* — propose only. - **`--apply`** — present proposal, prompt for approval, then write via `gh repo edit`. ## What this solves The description is the *single sentence* that decides whether a stranger clicks. It shows in: - GitHub search results - GitHub repo cards and "related repos" - Hacker News, Slack, Discord link previews (OpenGraph) - Package registries when the repo is linked from a package - LLM-driven "what tools exist for X" recall Bad descriptions are very common in the user's repos: ``` PRIVATE moat 🏰 M.O.A.T: Mixture of Adaptive Tokenizers PRIVATE bread 🥖 PRIVATE smoge 🐉🤖 PRIVATE sushi 🍣 PUBLIC gh-weekly <no description> PUBLIC papers <no description> PUBLIC x-ray <no description> ``` Emoji-only and empty descriptions kill discoverability for both humans and LLMs. ## What a good description looks like ``` ✅ "Workerd-based hypervisor with a declarative Cap'n Proto manifest. Substrate-level identity, audit, and per-bundle credential scoping. Today's primary application: hosting MCP servers behind one