git-workflow

You can automate changelog generation by parsing conventional commit messages from your Git history, mapping them to categories, and producing structured release notes automatically. This Skill processes your commit log to generate semantic versions and deployment steps.

Managing semantic versioning for feature branches involves analyzing commit history to determine version bumps automatically. This Skill evaluates your conventional commits to calculate the next semantic version and updates your package.json during the deployment procedure.

Yes, gitpython is required as a dependency to interact with Git repositories and parse conventional commit messages. It provides the underlying repository access needed to read commit history and generate release notes.

Yes, updating the package.json version during deployment is a core functional requirement. The workflow processes your latest commits, determines the appropriate semantic version bump, and applies it to your package configuration.

Semantic versioning with conventional commits works by mapping commit message prefixes to version bump types, such as features triggering minor bumps and fixes triggering patch bumps. This Skill automates that mapping to generate accurate release tags and changelog entries.

Yes, the workflow centralizes commit messaging with conventional-commit formats in Japanese. It parses these Japanese commit messages to categorize changes and generate the corresponding release notes.