repo-homepage-setlisted

<!-- Author: jamestexas — drafted by claude-opus-4-7 (2026-05-16) --> # /repo-homepage-set — GitHub Repo Homepage URL Set the `homepageUrl` field on a GitHub repository. This is the small link icon on the repo card's "About" panel. ## 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 homepage URL is the *one outbound link* GitHub gives a repository card. Setting it sends interested readers somewhere useful instead of nowhere. Surfaces: - Repo's About panel (top right of the repo page) - GitHub search results (shown below the description) - Topic browser cards - Some integrations (e.g. Slack unfurls) Most of the user's public repos have **no homepage set**, which means a visitor who's interested has no obvious "next step." ## Candidate sources, by priority For each repo, the homepage should be the *most useful* place a stranger could go after the README. In priority order: 1. **Dedicated docs site** — e.g. `docs.mache.dev`, `https://mache.io` 2. **Published package page** — `crates.io/crates/<name>`, `npmjs.com/package/<name>`, `pypi.org/project/<name>` 3. **Live demo / hosted app** — for things that have a runnable UI 4. **Org homepage** — for repos that are part of a named ecosystem (e.g. `agentic-research/*` → some `agentic