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

crush-commands

v1.0.0

Published

Install Crush commands from GitHub repositories

Readme

crush-commands

Install Crush commands from GitHub repositories.

Installation

No installation required! Just use npx:

npx crush-commands <owner>/<repo> --command <name>

Usage

Install All Commands

Install all commands from a repository:

npx crush-commands add <owner>/<repo>

Example:

npx crush-commands add myuser/my-crush-commands

Install a Specific Command

Install a specific command by name:

npx crush-commands <owner>/<repo> --command <name>

Example:

npx crush-commands myuser/my-crush-commands --command mycommand

Options

  • --command, -c <name> - Install a specific command (without .md extension)
  • --ref <branch|tag> - Use specific branch or tag (default: default branch)
  • --yes, -y - Skip confirmation prompts (useful for CI/automation)
  • --quiet, -q - Suppress non-essential output
  • --help, -h - Show help message
  • --version, -v - Show version number

Examples

Install all commands from the main branch:

npx crush-commands add myuser/my-crush-commands --ref main

Install a specific command without confirmation:

npx crush-commands myuser/my-crush-commands --command mycommand --yes

Install commands quietly (for scripts):

npx crush-commands add myuser/my-crush-commands --quiet

How It Works

  1. The tool fetches the crush/commands/ directory from the target GitHub repository
  2. It lists all .md files in that directory
  3. For each command file, it checks if it already exists in ~/.crush/commands
  4. If a file exists, it asks for confirmation before overwriting (unless --yes is used)
  5. It writes the command files to ~/.crush/commands/<name>.md

Repository Structure

The tool expects repositories to have the following structure:

my-repo/
└── crush/
    └── commands/
        ├── command1.md
        ├── command2.md
        └── command3.md

Each .md file should contain a Crush command definition.

Requirements

  • Node.js 18 or higher
  • Internet connection to access GitHub's public API
  • The target repository must be public and contain a crush/commands/ directory

Limitations

  • Only works with public GitHub repositories
  • Only installs .md files from crush/commands/ directory
  • Requires write permissions to ~/.crush/commands
  • GitHub API rate limits apply (60 requests/hour for unauthenticated requests)

After Installation

After installing commands, run:

crush reload

This refreshes Crush's command cache so the new commands are available.

Error Handling

The tool provides helpful error messages for common issues:

  • Repository not found: Verify the repository exists and is public
  • No commands found: Check that the repository has a crush/commands/ directory with .md files
  • Network errors: Check your internet connection
  • Rate limit exceeded: Wait before trying again

License

MIT