smaqit.release-git-local

Stage release files, commit, create an annotated tag, and push to remote.

3|1|Updated Feb 5, 2026

Search Tags:#git #version control #commit #release #push #tag

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the essential Git operations required to finalize and push a local release, ensuring your code is versioned and tagged correctly.

Core Features & Use Cases

Staging Release Files: Safely stages only the CHANGELOG.md and version files.
Committing Changes: Creates a dedicated commit for the release preparation.
Tagging Releases: Generates an annotated Git tag for the specific release version.
Pushing to Remote: Pushes both the release commit and the tag to the remote repository.
Use Case: After updating CHANGELOG.md and package.json for a new version, use this skill to commit these changes, tag it as v1.2.3, and push both to GitHub.

Quick Start

Use the smaqit.release.git.local skill to commit, tag, and push the release for version 1.0.0.

Frequently Asked Questions about smaqit.release-git-local

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

FAQPage Schema

How do I commit, tag, and push a local release to a remote Git repository?▼

Git release automation stages specified files like CHANGELOG.md, commits them with a release message, creates an annotated Git tag for the version, and pushes both the commit and tag to the remote repository.

What is the best way to automate staging only specific files like CHANGELOG.md for a version control release?▼

The best way to stage specific files for a release is to use an automated approach that safely stages only designated version files like CHANGELOG.md before committing, ensuring proper version control practices are followed without affecting other modified files.

Do I need Git installed and configured to push a local release commit and annotated tag?▼

Yes, you need Git installed and configured with appropriate repository access to push a local release commit and annotated tag. This ensures your local development release workflow has the required permissions to update the remote repository.

Can I create an annotated Git tag for a specific release version after updating package.json?▼

Yes, you can create an annotated Git tag for a specific release version after updating version files like package.json, generating a dedicated tag for the release and pushing it to the remote repository.

Why use an annotated tag instead of a lightweight tag when pushing a local release?▼

Using an annotated tag when pushing a local release is preferred because it stores metadata like the release message, ensuring proper version control practices are followed for your local development workflow compared to lightweight tags.

What files are staged during an automated local release commit workflow?▼

During an automated local release commit workflow, only specific release preparation files such as CHANGELOG.md and version files are safely staged, ensuring the dedicated release commit contains exactly the version control updates needed.