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

@meir-labs/skill-qa-army

v0.1.1

Published

A full QA regression run by an army of agents: the strongest model writes the test plan, automated, browser, and code-reading testers run rounds, and new verified issues become subtickets under one master regression ticket; reopened tickets are detached f

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

meirlabsmeirlabs

Keywords

claude-codeclaudecodexskillsskillqaregressiontestingplaywrightlinearmeirlabs

Readme

@meir-labs/skill-qa-army

A full QA regression of your app, run by a team of agents, ending in tickets — not fixes.

  1. The strongest model maps the app and writes a test plan.
  2. Testers run it in rounds, each matched to what it does best: automated suites, scripted browser cases, exploratory "real user" sessions, and code inspection.
  3. A verifier re-reproduces every candidate; what doesn't reproduce is dropped.
  4. Every confirmed issue becomes a subticket under one master regression ticket, rated for priority, severity, risk, and effort, and opening with a TL;DR anyone can read.

It never edits code. Tickets go to Linear, GitHub Issues, or local markdown files.

Install

# Claude Code — this project (./.claude/skills/qa-army)
npx @meir-labs/skill-qa-army

# Claude Code — every project (~/.claude/skills/qa-army)
npx @meir-labs/skill-qa-army --global

# Codex — this project / every project
npx @meir-labs/skill-qa-army --codex
npx @meir-labs/skill-qa-army --codex --global

Pass --force to overwrite an existing copy. Then ask your agent: "run qa-army on staging".

Read it before you run it: files/.

Reopened tickets

Whenever reopening a ticket in any project or team, including failed QA that returns it for further work, automatically clear its actual parent relationship without asking. Keep it parentless unless the user explicitly requests a parent; a plain reference link may remain for history. Preserve other fields except changes required by reopening. Read back and verify the reopened status and no parent; report any failure instead of claiming completion. Adding a comment to a ticket that is still open is not a reopening and must not detach it.