Today's TTY summary is accurate but flat: counts, spans, slugs. The data already inside the bundle can say much more interesting things without a single new byte leaving the machine.
Compare:
142 commits, TypeScript, React, 2021-2024
vs what the same bundle fields already support:
React since early 2021, sustained. Deepest work: payment webhooks (structural, cross-file). Peak intensity: Q3 2023. 84% of your commits are signed.
Same data, different sentence. The first informs, the second makes you want to screenshot it. For a tool whose whole first impression is one npx redential scan, the summary IS the product's front door.
Constraints (non-negotiable, same as ever)
- Derived ONLY from fields already in the bundle (principle 4: never a second data source, no enrichment)
- Deterministic, no LLM, no network
- Honest: no flattery inflation. If the repo is small, the summary says something true and modest, not fake grandeur
--json and piped output byte-identical as always; this is TTY presentation only
The ask
This is a design-first issue: propose summary lines (before/after pairs) grounded in real bundle fields (see schema/bundle.v1.json and src/summary.ts). Which fields combine into sentences people would actually share? What ordering puts the strongest true statement first? Mockups welcome in comments before any PR.
North star check: a summary people screenshot is a summary people trust and show around. That's distribution AND credential strength in one.
Today's TTY summary is accurate but flat: counts, spans, slugs. The data already inside the bundle can say much more interesting things without a single new byte leaving the machine.
Compare:
vs what the same bundle fields already support:
Same data, different sentence. The first informs, the second makes you want to screenshot it. For a tool whose whole first impression is one
npx redential scan, the summary IS the product's front door.Constraints (non-negotiable, same as ever)
--jsonand piped output byte-identical as always; this is TTY presentation onlyThe ask
This is a design-first issue: propose summary lines (before/after pairs) grounded in real bundle fields (see
schema/bundle.v1.jsonandsrc/summary.ts). Which fields combine into sentences people would actually share? What ordering puts the strongest true statement first? Mockups welcome in comments before any PR.North star check: a summary people screenshot is a summary people trust and show around. That's distribution AND credential strength in one.