Inspect git diffs and branches to automate staged commits, tags, and pushes.
npx skills add https://github.com/river-walras/virtus --skill git-auto-release
Please help me install this Agent Skill. Skill: git-auto-release Source: https://github.com/river-walras/virtus/tree/main/skills/git-auto-release Command: npx skills add https://github.com/river-walras/virtus --skill git-auto-release
This Skill helps teams ensure release integrity by reviewing git changes before committing, tagging, and pushing, reducing the risk of accidental commits or mis-tagging during releases.
Review the current git state and run the auto-release workflow to commit, tag, and push the release.
High-intent search queries and answers about installing and using this skill.
You can automate git release preparation by inspecting diffs and repository state to craft a coherent commit and tag strategy. This applies stage-aware commits, creates version tags based on repository state, and executes push operations respecting existing branches.
The safest way to create git tags for hotfixes is to review git changes and repository state before committing. This ensures release integrity by applying safeguards to avoid overwriting tags or pushing incomplete changes during the hotfix release workflow.
Automated release management handles branch conflicts by inspecting staged changes and repository state before executing operations. It includes specific checks to avoid conflicts and prevents pushing incomplete changes or mis-tagging during multi-branch release workflows.
Yes, you can use automated git tagging for feature branch releases. The workflow inspects diffs and repository state to determine if a release-worthy change exists, then automates staged commits and tag creation suited for coordinating multi-branch release workflows.
You need to inspect git diffs before pushing a release to reduce the risk of accidental commits or mis-tagging. Reviewing repository state ensures only release-worthy changes are committed and tagged, maintaining overall release integrity.
Limitations include relying on proper repository state and staged changes to avoid conflicts. You should not use automated release workflows when manual intervention is required for complex merge conflicts or when pushing incomplete changes that bypass safety checks.
fall-out-bugGenerate release artifacts and execute GitFlow merge operations for deployments.
u9401066Automate Git commit, push, and CI workflow triggering with pre-push validation.
mgd34msuGenerate pull request descriptions, commit messages, and release notes for Git workflows.
sunholo-dataAutomates end-to-end AILANG release management including pre-release checks, version bumps, changelog updates, git tagging, CI/CD verification, and release broadcasting.
