julienbrg
Add a spec in `notes/` and a TypeScript script in `scripts/` that finds public GitHub repos following GitHub Flow with an agent in the loop (a `CLAUDE.md` that scripts `gh` issue/PR commands), and ranks them as HuG Flow candidates by branch model, merge style, issue-linked PRs and activity. Why: the listing checklist names venues but no audience. These maintainers already run GitHub Flow through an agent, which is the flow HuG gates. Done when the spec describes the discovery queries, scoring signals, rate limits and output, the script produces a ranked JSON/CSV list with per-repo reasons, and the spec states the list is not for unsolicited issues or PRs.