npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@alexandrakay/pretty-pr

v0.1.7

Published

Your commits tell the whole story. Your PR should too.

Readme

prettypr

Your commits tell the whole story. Your PR should too.

prettypr turns your git history into clean pull request descriptions, changelogs, and reviewer notes — in seconds.

npx @alexandrakay/pretty-pr

The problem

Everyone knows what a good PR looks like. Nobody writes one at 4pm on a Friday.

You just shipped something. Your commit history says wip, fix, ok this works. The code is solid. The PR description is blank. Your teammate has no idea what they're reviewing.

prettypr reads your commits, understands what you built, and writes the copy your PR should have had.


Setup

You need an Anthropic API key.

export ANTHROPIC_API_KEY=sk-ant-...

Or drop it in a .env.local file at your repo root — prettypr picks it up automatically.


Usage

npx @alexandrakay/pretty-pr                   # commits only — fast, good enough for most PRs
npx @alexandrakay/pretty-pr --diff            # includes diff — richer output, better testing notes
npx @alexandrakay/pretty-pr --full            # everything: commits + diff + branch — best results
npx @alexandrakay/pretty-pr --base main       # compare against a specific base branch
npx @alexandrakay/pretty-pr --range abc..def  # specific commit range
npx @alexandrakay/pretty-pr --out pr.md       # write output to a markdown file
npx @alexandrakay/pretty-pr --open            # generate and open a GitHub PR (requires gh CLI)
npx @alexandrakay/pretty-pr --draft           # use with --open to open as a draft PR

Output quality ladder

| Mode | Command | Output | |------|---------|--------| | Commits only | npx @alexandrakay/pretty-pr | Decent PR title, okay description | | Commits + diff | npx @alexandrakay/pretty-pr --diff | Strong title, solid description, testing notes | | Commits + diff + branch | npx @alexandrakay/pretty-pr --full | Full picture — best title, reviewer notes, checklist |


What you get

Every run produces five sections:

  • PR Title — conventional commit style, max 72 chars
  • PR Description — what changed, why, how to test
  • Changelog Entry — ready to paste into your CHANGELOG.md
  • Reviewer Notes — what to focus on, what to skip, what's risky
  • Testing Checklist — auto-generated from your actual diff

Config file

Drop a .prettyrc file in your repo root to set team-wide preferences:

{
  "tone": "concise",
  "sections": ["title", "description", "changelog", "reviewer-notes", "testing-checklist"],
  "format": "markdown"
}

Tone options: balanced (default) · concise · detailed · formal

Generate your .prettyrc at pretty-pr.com/config.

prettypr reads .prettyrc automatically — no flags needed. Commit it to your repo and every teammate gets the same output format.


Open PRs directly

If you have the GitHub CLI installed and authenticated:

npx @alexandrakay/pretty-pr --full --open

prettypr generates the copy, opens a PR, and fills in the title and description. Add --draft for a draft PR.


Install globally

If you use it every day:

npm install -g @alexandrakay/pretty-pr
prettypr --full

Web app

Prefer the browser? Paste your commits at pretty-pr.com — no install, no signup.


License

MIT