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

@abhishekkkk15/readmegen-cli

v1.0.1

Published

Enterprise README Generator CLI

Readme

🖥️ @readme-gen/cli

The local-first AI documentation engine for your terminal.


📖 Overview

The readmegen CLI (also aliased as devcon) is a powerful tool for analyzing your local codebase and generating README files without ever leaving your terminal. It leverages the shared @readme-gen/analyzer package to extract project grounding evidence and provide state-of-the-art documentation generation.


⚙️ Core Commands

🚦 Quick Start

# Initialize your API keys and default provider
readmegen init

# Generate a basic README with default options
readmegen generate

# Preview the last generated README in your terminal
readmegen preview

🛠️ Config Management

# View your current CLI configuration
readmegen config view

# Update a specific provider's API key
readmegen config set-key <key> --provider groq

# Set the default model for all generations
readmegen config set-model <model-id>

# Reset all CLI settings to default
readmegen config reset

🏗️ Generation Flows

The CLI intelligently chooses between two distinct generation paths:

1. Semantic Local Flow (Default)

The Semantic Local Flow uses the analyzer package to build a structured project understanding locally. It handles:

  • Rewrite: Improving an existing README while preserving structure.
  • Append: Adding new grounded sections derived from code evidence.
  • Dynamic Context: Injecting extra business context into the generation.

2. Backend / Template Flow

The Backend Flow delegates generation to the API for more complex tasks:

  • Monorepo Templates: Using pre-defined layouts for complex projects.
  • Nested READMEs: Generating and saving multiple README files for sub-directories in a single pass.
  • Model Overrides: Forcing specific platform-hosted models.

💡 Advanced Usage

Skipping Interactive Prompts

If you provide a flag, the CLI is smart enough to skip that specific interactive prompt.

# This will skip the "tone" Selection and use "minimal" automatically
readmegen generate --tone minimal

Full Automated Generation

For CI/CD or non-interactive environments, use the --yes flag:

readmegen generate \
  --tone professional \
  --persona "Senior Developer" \
  --sections Installation Usage Features \
  --yes

Pacing LLM Requests

If you are working on a large repository and hitting Rate Limits (TPM), use the --llm-delay-ms flag:

readmegen generate --llm-delay-ms 30000

🛠️ Development

From the workspace root:

pnpm --filter @readme-gen/cli build
pnpm --filter @readme-gen/cli start