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

@onmax/wt

v0.1.0

Published

Git worktrees CLI with GitHub integration and Claude Code support

Downloads

205

Readme

wt

Git worktrees CLI with GitHub integration and Claude Code support.

Installation

npm install -g @onmax/wt

Prerequisites

  • GitHub CLI (gh) installed and authenticated
  • Claude Code (optional, for issue investigation)
  • Git repository with a GitHub remote

Usage

Run wt in any git repository to start the interactive mode:

wt

The CLI guides you through creating worktrees from issues, PRs, or custom branches.

Commands

| Command | Description | |---------|-------------| | wt | Interactive mode with prompts | | wt create <branch> | Create a worktree with a new branch | | wt create <branch> --pr | Create worktree and open a draft PR | | wt clone | Clone an existing PR as a worktree | | wt list | Show all worktrees with PR status | | wt sync | Pull latest changes from the base branch | | wt clean [pr] | Verify CI and prepare for merge |

Interactive Mode

When you run wt without arguments, the CLI presents an interactive menu:

  1. Create from Issue - Select an open GitHub issue, auto-generates branch name
  2. Create from PR - Clone an existing PR's branch as a worktree
  3. Create Custom - Enter a custom branch name

When creating from an issue, the CLI:

  • Creates a worktree at ../{repo}-worktrees/{branch}
  • Copies .env from the main repo if present
  • Pushes to your fork if you lack write access
  • Launches Claude Code in plan mode to investigate the issue

Configuration

Custom worktree paths can be configured per repository in ~/.config/wt/config.json:

{
  "nuxt-hub/core": "~/nuxt/hub-worktrees",
  "unjs/nitro": "~/nuxt/nitro-worktrees"
}

How It Works

The CLI uses git worktrees to maintain multiple working directories linked to a single repository. This approach:

  • Eliminates the need to re-clone repositories
  • Allows instant switching between branches via cd
  • Shares fetched objects across all worktrees
  • Enables working on multiple branches simultaneously

Fork Workflow

When you lack push access to a repository, the CLI automatically:

  1. Creates or uses your existing fork
  2. Adds the fork as a fork remote
  3. Pushes to the fork instead of origin
  4. Creates PRs with the correct user:branch head reference

License

MIT