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

@mikaelkaron/skills-cherry-pick-filter

v2.2.0

Published

<!-- generated-by: gsd-doc-writer -->

Readme

@mikaelkaron/skills-cherry-pick-filter

Sync a working branch to a clean target branch by cherry-picking commits that don't touch filtered path prefixes.

Part of the skills monorepo.

What it does

mks-cherry-pick-filter analyses commits on your current branch that are not yet on the target branch, then:

  1. Skips commits where every changed file matches a filtered path prefix (e.g. .planning/ notes, AI context files).
  2. Picks the remaining code-only commits onto the target branch in order.
  3. Halts before picking anything if it finds mixed commits — commits that touch both filtered paths and code paths — and reports exactly which files to split.

Human-readable output goes to stderr. When stdout is piped (not a TTY), one picked commit SHA is written per line, making it easy to chain with other git commands.

Installation

npm install @mikaelkaron/skills-cherry-pick-filter

Requires Node.js >= 22.18 and git on PATH.

As an mks plugin

If you use the mks CLI from this monorepo, install the package and it will be picked up automatically as the cherry-pick-filter plugin.

Usage

mks-cherry-pick-filter <targetBranch> --filter <prefix> [--filter <prefix>] [--dry-run]

Arguments

| Argument | Description | | -------------- | -------------------------------------------------- | | targetBranch | Branch to cherry-pick code commits onto (required) |

Flags

| Flag | Description | Default | | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | | --filter <prefix> | Path prefix to filter out. Repeatable. Commits where ALL changed files match are skipped; commits where SOME files match cause the command to abort. | — (required) | | --dry-run | Analyse and list commits without cherry-picking | false |

Examples

Sync current branch to beta, filtering out .planning/ commits:

mks-cherry-pick-filter beta --filter .planning/

Filter multiple path prefixes:

mks-cherry-pick-filter beta --filter .planning/ --filter .agents/

Dry run — analyse without cherry-picking:

mks-cherry-pick-filter beta --filter .planning/ --dry-run

Capture picked SHAs for downstream use:

mks-cherry-pick-filter beta --filter .planning/ | xargs git log --oneline

Mixed commit detection

If a commit touches files both inside and outside the filter prefixes, the command:

  • Lists every such commit with its filtered files and code files.
  • Exits without cherry-picking anything.
  • Prints the git rebase -i command to split each mixed commit.

Resolve all mixed commits first, then re-run.

Branch resolution

If targetBranch does not exist locally, the command checks origin and automatically tracks it before proceeding. If it is not found there either, the command exits with an error.

Environment

| Variable | Description | | --------- | ------------------------------------------------------------ | | GIT_CMD | Override the git executable path (defaults to which git) |

Running tests

npm test

Tests use a bundled fixture repository (test/fixtures/repo.bundle) and run against the compiled output.