PR-desc – generate PR descriptions from a Git diff, no AI required
It works fully offline, with zero runtime dependencies. An optional --ai flag will polish the wording with Claude if you want it — never required for basic use. If the key isn't set, --ai silently falls back to the plain, locally generated description — never required for basic usage.
- ▪It works fully offline, with zero runtime dependencies.
- ▪An optional --ai flag will polish the wording with Claude if you want it — never required for basic use.
- ▪If the key isn't set, --ai silently falls back to the plain, locally generated description — never required for basic usage.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,877 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/us702/pr-desc-cli |
| Publication time | Thu, 06 Aug 2026 11:58:06 +0000 |
| Retrieval time | 2026-08-06T12:10:43.748Z |
| Last seen | 2026-08-06T12:10:43.748Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Cj9LamH5EZi2 · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
pr-desc Turn a git diff into a ready-to-paste PR description — no more copying your diff into ChatGPT/Claude and asking "can you write a PR description for this?" every single time you open a pull request. npx pr-desc --branch main Before / after Without pr-desc With pr-desc git diff main npx pr-desc --branch main copy the whole diff (nothing to copy) paste into an AI chat (nothing to paste) type "write me a PR description for this" (nothing to ask) wait for a response, then reformat it markdown, ready to paste into GitHub, instantly Why Every PR needs a summary, a list of what changed, and a checklist — and most people generate that by hand-pasting their diff into an AI chat window.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.