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

@coldtea/pr-lens-agent-skill

v0.5.0

Published

The PR Lens skill for coding agents: author a graph document from a diff, validate it, render it, and correct a repository's map.

Readme

@coldtea/pr-lens-agent-skill

The PR Lens skill for coding agents. It teaches an agent to draw the change it just made: author a graph document from the diff, validate it against the contract, render it, attach it to the pull request, and to fix a repository's map by writing corrections rather than editing generated output.

MIT © Coldtea AI.

Install it

npm install --save-dev @coldtea/pr-lens-agent-skill

Claude Code: copy it where skills live, per project or per user:

mkdir -p .claude/skills/pr-lens
cp -R node_modules/@coldtea/pr-lens-agent-skill/{SKILL.md,references} .claude/skills/pr-lens/

Cursor: the same file works as a rule:

mkdir -p .cursor/rules
cp node_modules/@coldtea/pr-lens-agent-skill/SKILL.md .cursor/rules/pr-lens.mdc

Anything else: point your agent's instructions file at SKILL.md. It is plain markdown with YAML frontmatter, and it assumes nothing beyond a shell and npx.

What is in it

| | | | --- | --- | | SKILL.md | when to reach for PR Lens, and the write → validate → fix → render loop | | references/graph-document.md | the document, field by field, and what the validator will catch | | references/config.md | .github/pr-lens.yml corrections, with recipes |

The agent is usually the model. Rather than spending a provider key to describe a diff it already understands, it writes the document itself and lets pr-lens validate hold it to the contract. Every failure is a path into the document, so the loop closes without a human in it.

Why this exists

A coding agent that opens a pull request is asking a person to review code the person did not write. A diagram of what moved is the cheapest thing the agent can add to make that review possible.


Part of PR Lens. Review what actually matters.