smaqit.release-analysis

This Skill automates semantic versioning by analyzing git commit history, file diffs, and session history to classify change severity, suggesting the next MAJOR, MINOR, or PATCH release number with a rationale.

The best way to determine release version severity is by analyzing file modifications and commit logs against predefined criteria. This Skill assesses change impact to recommend whether a release should be a MAJOR, MINOR, or PATCH update.

Yes, git command-line access is required to analyze repository changes for versioning. The Skill executes git commands to gather commit history and file diffs, and optionally reads session history from the .smaqit/history/ directory.

Semantic versioning analysis handles session history by optionally reading records from the .smaqit/history/ directory. This session data is combined with git logs and file diffs to provide a comprehensive assessment of change impact for the version suggestion.

Yes, a rationale is provided for the suggested semantic version alongside the number. After assessing change severity from repository modifications, the Skill provides an objective recommendation for the version number and explains the reasoning behind it.

Automated release management should be used instead of manual version bumping before deploying a new software version. It reduces manual effort and potential errors by objectively evaluating code changes to calculate the appropriate MAJOR, MINOR, or PATCH increment.