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

@crown-dev-studios/skill-issue

v0.5.0

Published

First-party AI agent skills and companion CLIs for software development workflows.

Readme

skill-issue

First-party AI agent skills and companion CLIs for software development workflows. Built and maintained by Crown Dev Studios.

Install

The repo ships as one npm package with one version and multiple commands:

npx @crown-dev-studios/skill-issue second-opinion --help
npx @crown-dev-studios/skill-issue review-council --help

If you install it globally, you also get direct command names:

npm install -g @crown-dev-studios/skill-issue
skill-issue --help
second-opinion --help
review-council --help

skill-issue is the canonical release unit. second-opinion and review-council are published together from the same root package so their versions stay in sync.

What's in here

These are the first-party skills we use to keep our engineering standards high and our feedback loops tight.

| Skill | What it does | |---|---| | architecture-review | Reviews plans or implementations for model integrity, service boundaries, and canonical architecture direction using SOLID principles as a lens. | | brainstorming | Clarifies what should be built before planning begins. Resolves ambiguity in the problem, outcome, or direction through structured interview and option exploration. | | plan-review | Challenges and strengthens plans or brainstorms before implementation. Reviews for scope, product framing, sequencing, complexity, testing, operability, error handling, and threat model. | | planning | Creates a plan of record that serves as both spec and execution plan. Covers current state, constraints, invariants, model and API boundaries, architecture diagrams, phased execution, and proof strategy. | | testing-philosophy | Enforces our testing principles: what to test, how to structure tests, and when to push back on coverage theater. | | second-opinion | Asks a different AI agent for a second take on the current thread. Routes to Claude from Codex and Codex from Claude. | | linear-issue-shaping | Converts plans of record into Linear issues with dependencies, milestones, acceptance criteria, and sequencing. | | review-council | Runs parallel code reviews, then synthesizes and ranks the feedback to surface what actually matters. | | review-triage | Classifies and routes review feedback before implementation. Validates findings, assigns severity (P1/P2/P3), and routes to fix now, follow-up ticket, follow-up plan, or dismiss. |

Development

From the repo root:

pnpm install
pnpm run build
pnpm run test
pnpm run pack:dry-run

Local command entrypoints are also exposed as root scripts:

pnpm run second-opinion -- --help
pnpm run review-council -- --help

Packaging and release

The root VERSION file and package.json are the single source of truth. Release scripts live in scripts/ and are exposed as pnpm run release:*.

Preflight (no publish) — install with frozen lockfile, build, test, and dry-run npm pack:

pnpm run release:preflight

Bump the version (updates VERSION, package.json, lockfile metadata, then commits and tags vX.Y.Z):

bash scripts/bump-version.sh patch         # or minor | major | 1.2.3
bash scripts/bump-version.sh patch --no-push

Verify the tag matches VERSION and package.json:

bash scripts/check-version.sh --require-tag

Publish to npm (runs preflight, pushes branch + tag, then pnpm publish). Requires npm login, a clean git tree, and the matching vX.Y.Z tag:

bash scripts/deploy.sh --dry-run           # preview
bash scripts/deploy.sh                     # publish

The pnpm run release:* aliases invoke the same scripts but do not forward extra flags cleanly, so call the scripts directly when passing options. pnpm run release:preflight remains the convenient no-arg entry point for the preflight.

Full release sequence:

bash scripts/bump-version.sh patch
bash scripts/check-version.sh --require-tag
bash scripts/deploy.sh

License

MIT