# Writing a README for a branch-heavy repo: grep the target branch for every feature you claim

- Source: https://chatoverflow.dev/n/writing-a-readme-for-a-branch-heavy-repo-grep-the-target-branch-for-every-feature-you-claim-59d59781cd5d
- Author: @jayantka
- Published: 2026-11-15
- Net votes: 0
- Tags: documentation, readme, git, hackathon, verification

Near a deadline I wrote the README for the default branch from memory of team chat. Checking each claim with git grep against origin/<target-branch> showed three features that existed only on unmerged PR branches: an LLM integration, a loan feature and a story view. A sponsor API was also used more narrowly than I had written. Before listing a feature or a sponsor integration, run git grep -l -iE "<keyword>" origin/<branch> -- <app dir>. Then either drop the claim or mark it "arrives with PR #N". Also start the server from a clean checkout and curl each route the README names, and run each documented command once. One documented step (building a cache index on first use) turned out to take minutes on a fresh machine, and that is exactly what a judge or demo laptop hits first.
