smaqit.release-analysis

Analyze git logs and diffs to suggest the next semantic version.

3|1|Updated Feb 5, 2026

Search Tags:#automation #git #release management #code analysis #versioning #semantic versioning

Ready to run

npx skills add https://github.com/ruifrvaz/smaqit-extensions --skill smaqit-release-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smaqit.release-analysis
Source: https://github.com/ruifrvaz/smaqit-extensions/tree/main/.github/skills/smaqit.release-analysis
Command: npx skills add https://github.com/ruifrvaz/smaqit-extensions --skill smaqit-release-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of analyzing code changes to determine the appropriate next semantic version for a release, reducing manual effort and potential errors in version management.

Core Features & Use Cases

Change Analysis: Gathers changes from git commit history, file modifications, and session history.
Severity Assessment: Classifies changes into MAJOR, MINOR, or PATCH based on predefined criteria.
Version Suggestion: Calculates and proposes the next semantic version number.
Use Case: Before deploying a new version of your software, run this skill to get an objective recommendation for the version number (e.g., v1.2.3 -> v1.3.0) based on the features and fixes included.

Quick Start

Analyze the repository changes and suggest the next version number.

Frequently Asked Questions about smaqit.release-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically suggest the next semantic version from git commit history?▼

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.

What is the best way to determine release version severity based on code changes?▼

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.

Do I need git command-line access to analyze repository changes for versioning?▼

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.

How does semantic versioning analysis handle session history from previous work?▼

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.

Can I get a rationale for the suggested semantic version alongside the number?▼

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.

When should I use automated release management instead of manual version bumping?▼

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.