conventional_commit
0.6.1+1, released a year ago by invertase.io
Parse a git commit message using the Conventional Commits specification.
What it does
Parses git commit messages into structured data according to the Conventional Commits specification. It extracts components such as description, body, type, scopes, breaking changes, and footers.
AI-written summary of version 0.6.1+1, based on the package's README and metadata. Report an inaccuracy
Use it when
- You are building changelog generation tools or release management utilities.
- You need to validate commit messages against conventional commit standards in Dart or Flutter.
Skip it when
- You do not need to parse or validate git commit strings.
Strengths
- Provides a simple API for extracting all parts of a conventional commit message.
- Handles edge cases like multi-line bodies, custom types, and breaking changes.
Weaknesses
- Very narrow and specialized scope.
Setup
- Kind
- Pure Dart
- Effort
- Low
- Code generation
- No
- Direct dependencies
- 0
import 'package:conventional_commit/conventional_commit.dart';
void main() {
final parsedCommit = ConventionalCommit.parse('feat(cool): An exciting new feature.');
print(parsedCommit.type);
}Alternatives
Packages that do the same job and could replace conventional_commit.
- msgpack_dart
MessagePack implementation for Dart
50Compare - commitlint_cli
CLI tool that lints commit messages against the Conventional Commits spec.
42Compare - pkcs7
Parse, generate, and verify PKCS#7 messages and X509 certificates
50Compare
Works with
Packages commonly used together with conventional_commit: ones it builds on, ones built on it, and its own family.