Add "commit": "commitprompt", then run it with npm, pnpm, or Yarn.
commitprompt · ~/project
$ pnpm commit
Select the type of change:
1. feat A new feature
2. fix A bug fix
3. docs Documentation only
Type: 1
Scope: cli
Description: add repository-aware validation
feat(cli): add repository-aware validation
Create this commit? [y/N] y
Commit created with the repository’s rules.
Runtime
Node 22+
Package managers
npm · pnpm · Yarn
Configuration
Your Commitlint rules
One small command
Built around your repository
No adapter configuration and no package-manager lock-in. Commitprompt stays focused on the moment between staging changes and creating the commit.
Your rules
Loads the repository’s Commitlint configuration and validates before Git receives the message.
Your package manager
Runs the same through pnpm, npm, or Yarn because validation happens through Commitlint’s API.
Your final say
Shows the complete message—including body, breaking change, and issue references—before committing.
The whole workflow
Stage. Prompt. Commit.
The happy path stays short, while every guardrail remains visible and testable.
1Stage the changeCommitprompt stops early when the index is empty.
2Answer focused promptsChoose a type, scope, subject, and optional details.
3Validate and confirmCommitlint checks the complete message before Git sees it.
Complete when you need it
Small prompt. Full commit.
Keep the common case quick, then add the detail that makes a change useful to humans and release tooling.
