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

@sirasagi62/chizu

v0.1.2

Published

A command-line tool that summarizes the code contained in a repository

Readme

🗺️ chizu

chizu (Japanese for "map") is a lightweight CLI tool to generate a concise repository map of your codebase. It extracts key entities like classes, functions, and methods while respecting your project's structure—perfect for giving LLMs (like ChatGPT, Claude, or Gemini) and coding agents (like Claude Code, Gemini CLI or opencode) the right context without wasting tokens.

Powered by code-chopper.

✨ Features

  • AST-based Extraction: Uses Tree-sitter to identify meaningful code boundaries rather than just regex patterns.
  • AI-Optimized: Generates a high-density "map" of your repo to help AI understand your codebase's architecture.
  • Smart Filtering: Automatically respects .gitignore and ignores noisy directories (node_modules, .git, etc.).
  • Safe Concurrency: Built-in concurrency control to prevent EMFILE errors even on massive repositories.
  • Compress Mode: A dedicated mode to show only signatures for maximum token efficiency.
  • Targeted Search: Filter the map by specific keywords to find relevant functions or classes instantly.

🚀 Quick Start

You can run it instantly via npx:

npx @sirasagi62/chizu [directory]

Or install it globally:

npm install -g @sirasagi62/chizu

📖 Usage

Basic Map

Generate a map of the current directory:

chizu

Compress Mode

Show only signatures/definitions (ideal for large repos):

chizu --compress

Specific Directory

chizu ./src

Search by Keyword

Find only entities containing "fetch" (useful for identifying API logic):

chizu -q fetch

Case-Insensitive Search

Search without worrying about uppercase/lowercase:

chizu -q user -i

🛠️ CLI Options

| Option | Shorthand | Description | Default | | :--- | :--- | :--- | :--- | | directory | - | The target directory to map | . | | --compress | -c | Only show signatures and hide docs/bodies | false | | --query <text> | -q | Filter entities and files by a search keyword | - | | --ignore-case | -i | Ignore case distinctions when searching | false | | --help | -h | Display help information | - |

💡 Why chizu?

When working with AI, pasting entire files is often overkill and hits context limits. chizu creates a "table of contents" for your code, allowing the AI to see how everything connects before you dive into specific implementation details. Instead of mapping the whole repo, use --query to pinpoint specific logic across multiple files, giving the AI exactly the context it needs for a specific task.

Acknowledgement

This tool is inspired by aider's repomap.

License

MIT