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

linear-hierarchy-guard

v1.0.0

Published

Claude Code / agent skill: review Linear issues before promotion, enforce the Issue/Project/Milestone/Initiative hierarchy, and preserve deadline integrity so work doesn't sprawl into a million unrelated tickets.

Vulnerabilities

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

Links

Git

Maintainers

adamsandadamsand

Keywords

linearclaude-codeclaude-skillagent-skillproject-managementagent-workflow

Readme

linear-hierarchy-guard

A Claude Code / agent skill for reviewing a Linear issue or spec before an agent starts executing it, and deciding whether it should stay a single issue or be promoted into a project, milestone set, or initiative — so a team ends up with a clean, correctly-nested hierarchy instead of a million loose, unrelated issues.

What it does

When an agent is handed a Linear issue, PRD/spec, /wayfinder map, /to-spec output, or /to-tickets output, this skill:

  • Fetches the live Linear state for the issue (status, due date, cycle, project, initiative, parents, blockers, comments, etc.) instead of trusting only the prompt text.
  • Classifies the work using a Promotion Decision Matrix: keep as issue, convert to a parent/control issue, promote to a project, add milestones, or attach to an initiative.
  • Runs a Deadline Integrity Algorithm so that promoting an issue into a bigger structure never silently loosens its original due date. Every derived project, milestone, ticket, or cycle assignment must inherit the seed issue's deadline unless a human explicitly approves changing it.
  • Requires breadcrumbs: every promoted project/issue links back to the original seed issue, and the seed issue gets a clear final disposition (kept, converted to control issue, closed as promoted, or retained as intake).
  • Refuses to fabricate dates, duplicate existing structure, or mark anything "Done" purely from a planning/restructuring pass.

The core failure mode this prevents: a ticket due July 15 gets "promoted" into a new project whose milestones/tickets end up dated July 20 (or undated), quietly breaking the original commitment.

Install

From the root of your project:

npx linear-hierarchy-guard

This copies SKILL.md into .claude/skills/linear-hierarchy-guard/ in the current directory. Restart Claude Code (or reload skills) afterward.

No install script, no postinstall hooks — it just copies two files into place. Feel free to read bin/install.js before running it.

Usage

Invoke it before /to-tickets, before assigning a coding agent to a large issue, or whenever an issue starts to look like it's actually a workstream.

See SKILL.md for the full decision matrix, deadline algorithm, templates, and write procedure.

License

MIT