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 🙏

© 2024 – Pkg Stats / Ryan Hefner

c-commit-cli

v0.1.6

Published

A CLI tool to create conventional git commit messages in terminal.

Downloads

2

Readme

Git Conventional Commits CLI

Generate conventional commit messages from the command line.

I liked using conventional commits extension on VS Code and wanted to have a similar experience on the terminal.

This CLI is inspired by the Conventional Commits specification.

Installation

Make sure you have node.js installed on your system. You can download it from here.

Run the following command to install the CLI globally.

npm i c-commit-cli -g

You can now run commit from any directory.

Usage

Make sure to stage your changes before running the command.
The goal of the CLI is to help you generate conventional commit messages and not manage your git workflow.

Run commit to initiate the commit process.

What type of commit are you making?

The first prompt is about the type of commit you are making. Following are the options you can pick from.

Select commit type

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
  • ci: Changes to our CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

To be added in the future

  • wip: Work in progress
  • release: Release a new version
  • deps: Update dependencies
  • security: Fix security issues
  • breaking: Introduce breaking changes

Select a Gitmoji

The second prompt is about selecting a Gitmoji. Gitmoji is an emoji guide for your commit messages. You can find more about it here.

Select Gitmoji

If you don't want "Type" or "Gitmoji", you can skip them.

Commit message and details

You will be prompted to enter a commit message and an optional detailed description of the changes you made.

Commit message and details

If you want to add a detailed description, you will be taken to your default editor to write the description. The changes made and saved in the editor will reflect in the terminal once you close the editor.

Commit message preview

On the final stage you will get a preview of the commit message. You can either confirm the message or go back to make changes.

Commit message preview

Feedback

Feel free to open an issue if you have any feedback or suggestions. I would love to hear from you.

If you want to contribute, please open a pull request.