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

@canthisbeautomated/commitchangelog

v0.5.2

Published

Manage your changelogs in your commits and generate a shorter, friendlier CHANGELOG

Readme

commitchangelog

Manage your changelogs in your commits and generate a shorter, friendlier CHANGELOG

Having a CHANGELOG.md file ist all fine, but often merge conflicts arise, when including Unreleased changes. This CLI-Tool should solve that, and provide ways to add formatted, human readable changes for example in merge requests or release notes.

Usage

Collecting changes

  • The format is based on Keep a Changelog.
  • The changes are embedded in your commit bodies using the keywords from Keep a Changelog.
  • Not all commits have to have a [changelog] block. If there is no relevant change in the commit, is may be left out.

Example:

refactor: es6

[changelog]
changed: refactored to es6
removed: gitlog dependency

CLI

Usage: gitccl [options] [command]

Options:
  -V, --version   output the version number
  -h, --help      display help for command

Commands:
  full            display a full Markdown with all releases (inkl. Unreleased)
  write           write the full Markdown with all releases (inkl. Unreleased) into a file
  unreleased      Display markdown from the unreleased changelog entries
  tag             Display markdown a specific tag
  compare         Display markdown of the changes between git revisions
  compare-head    Display markdown of the changes between HEAD and a chosen git revision/branch/tag
  help [command]  display help for command

npx

# Displays help message as seen above
npx gitccl

Requirements

  • git

Install

With npm installed, run

$ npm install --save-dev @canthisbeautomated/commitchangelog

Acknowledgments

commitchangelog was heavily inspired by git-cl.

Changelog

The changelog of this CLI Tool may serve as an example:

See CHANGELOG.md.

License

MIT