docs(readme): tighter tagline; drop misleading 500-commit corpus number#196
Merged
Conversation
…ng to solo devs The '500 commits' references implied repowise mines only the last 500 commits of the repo. That isn't accurate — co_change_commit_limit is per-file, not a global corpus cap. Replace the specific numbers with 'git history' / 'configurable depth' so the README doesn't undersell larger histories or contradict the actual default. Also rebalance the framing: the intro and git-intelligence sections read as engineering-team-only, but most of these signals (hotspots, ownership concentration, contributor profile, bus factor, decisions) are equally useful for solo devs returning to their own code months later. Call that out directly so individual users see themselves in the README.
- New tagline: 'The codebase intelligence layer for your AI coding agent.' The previous one tried to enumerate the audience and was too long. - The '500 commits' references implied repowise mines only the last 500 commits of the repo. That isn't accurate — co_change_commit_limit is per-file, not a global corpus cap. Replace with 'git history' / 'configurable depth' so the README doesn't undersell larger histories or contradict the actual default. - Soften 'engineer' / 'engineering-leader' framing to 'author' / per-module rollup so the language doesn't read as team-only when most of these signals are equally useful on a solo repo. Kept the change subtle — no per-bullet 'solo vs team' callouts.
swati510
approved these changes
May 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The codebase intelligence layer for your AI coding agent.The previous tagline tried to enumerate the audience (solo devs / engineering teams) and was too long.co_change_commit_limitis actually a per-file limit, not a repo-wide cap. Replaced with neutral phrasing ('git history', 'per-file, configurable depth') so the README doesn't undersell larger histories or contradict the actual default inconfig.yaml.Test plan
git: co_change_commit_limit: 500config block (which is the real default).Git IntelligenceandGit intelligencesections — confirm wording reads as inclusive without the explicit 'solo vs team' callouts.