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

llm-coding-toolkit

v0.3.1

Published

CLI toolkit for developers using LLM coding agents

Readme

LLM Coding Toolkit

A CLI with helpful commands for coding with LLMs.

Requirements

  • Node.js 20+
  • A GitHub token with Pull requests (read-only) permission

Install

bun install -g llm-coding-toolkit
pnpm install -g llm-coding-toolkit
npm install -g llm-coding-toolkit

Usage

llmct <command> [options]

Run llmct <command> --help for command-specific options.

Commands

| Command | Description | | --- | --- | | review-comments | Collect unresolved PR review comments into a markdown file to pass to an LLM agent | | prs | List open pull requests for a repo | | add-token | Add a GitHub API token | | list-tokens | List configured tokens | | autocomplete | Install shell autocomplete for llmct | | messages | Manage reusable message templates with variable substitution |

Examples

# Collect unresolved PR review comments for an LLM agent (auto-detects repo)
llmct review-comments

# Collect review comments for a specific repo
llmct review-comments --repo owner/repo

# List open PRs (auto-detects repo from git remote)
llmct prs

# List open PRs for a specific repo
llmct prs --repo owner/repo

# Add a token (press Enter for default, or enter an owner/org)
llmct add-token

# List configured tokens
llmct list-tokens

# Install shell autocomplete for the current shell (zsh/bash/fish)
llmct autocomplete

# Pick a saved message, fill in variables, and copy to clipboard
llmct messages

# Add a new message template
llmct messages add

# Update or remove a message template
llmct messages update
llmct messages remove

The review-comments command fetches unresolved review threads from a PR, strips bot noise (HTML, Cursor/Greptile links), and writes a clean markdown file to .llm-coding-toolkit/agent-reviews/. If there's a single open PR it's auto-selected; otherwise an interactive picker is shown.

It also ensures .llm-coding-toolkit/ is added to your repo .gitignore.

The messages command lets you save reusable message templates with variable placeholders ({{VarName:"default"}}). When you pick a message, you're prompted to fill in variables, and the resolved text is copied to your clipboard. Templates are stored in ~/.config/llm-coding-toolkit/messages.json.

Authentication

Before running review-comments or prs, add a GitHub token:

llmct add-token
  • Press Enter at the owner prompt to store a default token.
  • Enter an organization/owner name to store a token for that specific owner.
  • Tokens are stored in ~/.config/llm-coding-toolkit/config.json.

Stack

  • Runtime: Bun — TypeScript executed directly, no build step needed for dev
  • GitHub API: @octokit/rest
  • Interactive prompts: @clack/prompts
  • Terminal colors: picocolors
  • Linting: ESLint + Prettier + typescript-eslint

Development

Run locally

./cli.ts <command> [options]

Build

make build

Compiles to dist/cli.mjs (Node-compatible).

Lint

make lint        # check for issues
make lint-fix    # auto-fix ESLint issues + type check

License

MIT