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

@skitterbyte/skitterspec-github

v2.3.0

Published

Spec-driven development for Claude Code, with one-way GitHub sync — a superset of @skitterbyte/skitterspec: the base filesystem workflow plus /spec-status · /spec-push · /spec-claim and the spec-sync CLI, mirroring specs to GitHub Issues, sub-issues and a

Vulnerabilities

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

Links

Git

Maintainers

reuben.greavesreuben.greaves

Keywords

claudeclaude-codespec-driven-developmentsddskillsscaffoldgithubgithub-projects

Readme

@skitterbyte/skitterspec-github

Spec-driven development for Claude Code, with one-way GitHub sync — a superset of @skitterbyte/skitterspec: the base filesystem workflow plus /spec-push · /spec-status · /spec-list · /spec-claim and the spec-sync CLI. The repo is canonical; GitHub is a generated mirror.

Install exactly one distribution — this, the base, or one other superset — never two:

npx @skitterbyte/skitterspec-github init

What the sync is

  • A spec is a GitHub issue; each phase a sub-issue; tasks ride along as a task list in the body (still a read-only mirror — the repo wins on every push).
  • Workflow state lives on a Projects v2 board. An issue is only open or closed, so each lifecycle bucket maps to an option of the board's Status field; complete and cancelled also close the issue (completed / not_planned). The board is required — one per repo.
  • One-way: nothing is read back into the repo, and skitterspec tells the board only about its own transitions — a card moved by hand is left alone. A body edited on GitHub — a ticked box included — is reported and replaced on the next push, loudly.
  • Releases are yours to record: spec-sync released <range> --json lists exactly the issues a range contains, by their Refs: #N trailers, each with its spec and url. Your CI pipes that into whatever records a release or a deploy; skitterspec writes neither.
  • Assignment: /spec-start assigns the issue to your login; /spec-claim hands it on. Only collaborators can be assigned, and that is checked before anything is written.
  • Intake: spec-sync intake lists issues waiting to become specs, routed to /spec, /spec-bug or /spec-hotfix by label.

Setup

Everything here is free on a personal account. You need a Projects v2 board and a classic token with the repo and project scopes. /spec-github-setup interviews you and writes specs/.core/github.config.json (owner, repo, board number, bucket→Status options). Keep the token out of the repo — export GITHUB_TOKEN, or:

skitterspec-github spec-sync credentials set

skitterspec-github spec-sync doctor --check-remote reports readiness across every layer, token scopes included.

Not yet shipped for GitHub: retarget, reattach, spec-sanitise.

This package's bin/, src/ and assets/ are composed at build time from the skitterspec monorepo — see the repo for sources and development.