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

@juicerq/ralph

v0.9.0

Published

Orchestrate Claude Code agents to implement GitHub issues in parallel

Readme

@juicerq/ralph

Orchestrate Claude Code agents to implement GitHub issues in parallel.

Workflow

Ralph is the final step of an AI-powered development workflow:

  1. /grill-me — Design review. Get grilled about every aspect of your plan until reaching shared understanding
  2. /write-a-prd — PRD creation. Turn the validated design into a detailed product requirements document
  3. /prd-to-issues — Issue breakdown. Break the PRD into independently-implementable GitHub issues
  4. bunx @juicerq/ralph — Automated implementation. Ralph picks up the issues and implements them in parallel

Usage

bunx @juicerq/ralph

Ralph will:

  1. Fetch open issues with the configured label (default: ralph)
    • If none found and running in a TTY, opens an interactive selector to pick from all open issues
  2. Run a planner agent (Opus) to analyze dependencies and order issues
  3. Spawn parallel Claude Code agents to implement each issue in isolated git worktrees
  4. Merge completed work back to the current branch
  5. Auto-resolve merge conflicts using Claude Code

CLI Flags

bunx @juicerq/ralph --label my-label --concurrency 5 --model sonnet

| Flag | Default | Description | |------|---------|-------------| | --label | ralph | GitHub issue label to filter | | --concurrency | 1 | Max parallel agents | | --model | opus | Default model (planner may override per issue) | | --prompt | built-in | Extra instructions for implementer agents |

Configuration

Optional ralph.config.ts in your project root:

import type { Config } from "@juicerq/ralph"

export default {
  label: "ralph",
  concurrency: 1,
  model: "opus",
  prompt: "Run bun typecheck and bun test before committing.",
} satisfies Config

Priority: CLI flags > ralph.config.ts > defaults

How it works

bunx @juicerq/ralph
  |
  1. Load config (defaults -> ralph.config.ts -> CLI flags)
  2. gh issue list --label <label> --state open
  3. Planner (Opus) analyzes dependencies, assigns model per issue
  |    opus = complex tasks | sonnet = trivial tasks
  4. For each issue (up to --concurrency):
  |    git worktree add .ralph/<number> -b ralph/<number>
  |    claude -p --model <model> (runs in worktree)
  |    git merge ralph/<number> (back to current branch)
  |    cleanup worktree + branch
  5. Resolve merge conflicts with Claude Code
  6. Summary: success/fail per issue

On unresolvable conflict, the branch is preserved for manual resolution. On failure, the branch is preserved for inspection.

Requirements