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

@cleepi/git

v0.2.1

Published

Cleepi git conventions: conventional-commit + branch-naming + PR-shape skills, with /commit and /pr prompts. Monorepo-aware domain and ticket-id resolution. Subject-line-only commits; no body, no footers, no Co-authored-by ever. Small modular PRs; title d

Readme

@cleepi/git

Cleepi's git conventions as a pi package. Install in any repo where you want a clean, standardised commit history — and never another Co-authored-by: Claude line ever again.

What's in the box

  • skills/git-commit/SKILL.md — commit-message convention (Conventional Commits + AngularJS types, monorepo-aware domain, ticket-id discipline).
  • skills/git-branch/SKILL.md — branch naming convention: <type>/<ticket>-<slug> with ticket optional.
  • skills/git-pr/SKILL.md — PR/MR shape: title from branch, body 1–3 sentences + optional bullets. PRs should be small and modular.
  • /commit <type> <message> — resolves domain + ticket, assembles the message, strips Co-authored-by:, asks before committing.
  • /pr [<description>] — derives title from current branch, detects GitHub/GitLab, runs gh pr create / glab mr create or prints for manual paste.

The 30-second version

Every cleepi commit follows this shape:

<type>(<domain>): [<ticket-id> ]<message>

Examples:

feat(crew): AC-201 add reviewer pre-step
refactor(sdd): AC-202 collapse Why-now into Why
docs(crew): fix README install path
chore(meta): bump prettier
fix(atlassian): DRAFT-007 handle empty JQL response

Hard rules (non-negotiable):

  • One line. No body. No footers.
  • NEVER Co-authored-by:. Not for AI assistants. Not for anyone. Strip it if your tooling tries to add it.
  • No Signed-off-by: either.
  • No emoji, no trailing period.
  • Imperative, present tense, lowercase first letter of message.

For the full discipline (type table, domain rules, ticket-id resolution chain, anti-patterns, voice), see skills/git-commit/SKILL.md. It's the source of truth.

Install

Global (every pi session gets the convention):

pi install git:github.com/cleevio/cleepi/packages/git

Project-local (recommended for repos adopting the convention as their actual standard):

cd <repo>
pi install -l git:github.com/cleevio/cleepi/packages/git

How /pr works

/pr Rename the primary button per the AC-123 redesign.
  1. Reads the current branch: feat/AC-123-rename-primary-button.
  2. Derives title mechanically: feat(AC-123): rename primary button. No diff reading.
  3. Uses your description as the body (or asks if you didn't pass one). Bullets optional, never invented.
  4. Detects host from git remote get-url origin.
  5. Shows you title + body + host. Asks [y / N / edit].
  6. Runs gh pr create / glab mr create, or prints for manual paste if neither CLI is installed.

If the branch doesn't match <type>/..., /pr refuses and tells you to rename the branch first. The point of the convention is that the title is mechanical.

How /commit works

/commit feat add reviewer pre-step
  1. Validates feat against the Angular type set.
  2. Resolves domain: cwd is inside packages/crew/crew.
  3. Resolves ticket-id: cwd is under docs/AC-201-reviewer-prestep/AC-201.
  4. Assembles: feat(crew): AC-201 add reviewer pre-step.
  5. Strips any Co-authored-by: injected anywhere.
  6. Shows you the message + the staged diff summary.
  7. Asks [y / N / edit] before running git commit.

If you call /commit outside a packages/<n>/ directory, or on a branch with no ticket pattern, it asks you for the missing pieces. Manual --domain=... and ticket-id tokens in the args always win.

Tuning

Don't edit the package source — it gets overwritten on pi update. Instead, copy the skill into your project (or user) scope and edit there:

cp .pi/agent/skills/git-commit/SKILL.md .pi/skills/git-commit/SKILL.md
cp .pi/agent/skills/git-branch/SKILL.md .pi/skills/git-branch/SKILL.md
cp .pi/agent/skills/git-pr/SKILL.md     .pi/skills/git-pr/SKILL.md
# edit the copy in .pi/skills/

Project scope wins on collision.

Soft-aware integration with @cleepi/sdd

/commit and @cleepi/sdd's /journal share the same ticket-id resolution chain (cwd → branch → ask). When sdd is installed alongside git, ticket detection is consistent. When it isn't, branch-name and ask-user fallbacks still work.

There is no hard dependency.

Related