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

@manufac/sculptor

v3.3.0

Published

A library for claude code review

Readme

@manufac/sculptor

CLI that sets up Claude guidelines, skills and GitHub workflows in a TypeScript project.

Usage

Run from the root of your repository:

npx @manufac/sculptor init

sync does the same thing. Use it to pull in newer guidelines later.

Use --all to install every skill, without checking your dependencies:

npx @manufac/sculptor init --all

What it installs

| Location | Content | | -------------------- | ---------------------------------------------------------- | | .claude/skills/ | Coding convention skills and the dependency upgrade skills | | .github/workflows/ | Code review and dependency upgrade workflows | | .github/prompts/ | Prompts used by the code review workflow |

Existing files with the same name are overwritten.

Convention skills

A skill is installed only when its package is a dependency in the root or any workspace package.json.

| Dependency | Skill | | ----------------------- | ---------------------------------------------------------------- | | typescript | typescript-coding-conventions, typescript-naming-conventions | | react | react-conventions | | zod | zod-conventions | | @mantine/core | mantine-core-conventions | | @mantine/hooks | mantine-hooks-conventions | | @mantine/form | mantine-form-conventions | | mantine-datatable | mantine-datatable-conventions | | @tanstack/react-query | tanstack-query-conventions | | @tanstack/react-table | tanstack-table-conventions |

Dependency upgrade skills

These are always installed:

  • deps-upgrade-patch: patch updates in one pull request.
  • deps-upgrade-minor: minor updates in one pull request, stacked on the patch branch. 0.x minor updates are marked "Needs review".
  • deps-upgrade-major: one pull request per major update, stacked one on top of another. Claude fixes the breaking changes, tries at most 2 times for each update, and lists what could not be updated in the last pull request.

Workflows

Code review (inline.yml)

Reviews a pull request when it is opened, and again when someone comments @claude-inline on it.

Deps Upgrade (deps-upgrade.yml)

Runs by hand (workflow_dispatch). In one job it runs the patch, minor and major skills in that order. The branches are named deps/update-<run id>-patch, -minor and -major-<package>-<version>.

The job detects the package manager from the lock file (yarn, pnpm or npm), uses the Node version from .nvmrc, and caches that package manager.

Merge the pull requests in stack order: patch, then minor, then each major.

Setup in the target repository

  1. Add the secret CLAUDE_CODE_OAUTH_TOKEN to the repository.
  2. Add a .nvmrc file with your Node version.
  3. In Settings, then Actions, then General, allow GitHub Actions to create pull requests.
  4. Turn on "Automatically delete head branches". Stacked pull requests then move to the main branch by themselves when the one below is merged.

Development

yarn build          # compile and copy the skills, workflows and prompts into dist
yarn sculptor:init  # run init using the built files

Edit the files in src/. The copies in .claude/ and .github/ are generated by init.

See Testing.md for how to test the prompts.