How do I install the Git Workflow skill?

Run npx skillmds@latest add sharex/git-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Git Workflow skill do?

Commit, push, or version XerahS changes. Use only when the task includes these operations. It is listed under Productivity on SkillMD.

Is Git Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Workflow?

sharex (@sharex) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Workflow by sharex — Agent Skill

Name: Git Workflow
Author: sharex

File contents

Git and versioning

Follow the wrapper and fallback guidance in AGENTS.md.

Version and commit format

Root Directory.Build.props supplies the app version. Before an app commit, compare it with the highest existing XerahS release tag; the version must be strictly greater. If needed, bump it to the next unreleased version.
App commits use [vX.Y.Z] [Type] Concise description, with types such as Fix, Feature, Build, Docs, or Refactor.
Shared-library/submodule commits, including ShareX.ImageEditor, use [Type] Concise description without the app version.
For requested version increments: fixes increment patch; features increment minor and reset patch; breaking changes increment major and reset minor/patch.
Do not put app versions in individual project files. Synchronize other tracked props only if they intentionally carry the XerahS app version; do not overwrite independent library versions.
Release automation synchronizes derived Chocolatey metadata and validates the generated package.

Verification and integration

Inspect status, the task diff, tracking branch, and submodule state before staging. Preserve unrelated edits. Pull/rebase or update submodules when integration requires it, after checking that local work will be preserved; do not unconditionally pull into a dirty checkout.

Before pushing code or build configuration, run the desktop solution build required by AGENTS.md and relevant tests. Do not disable warnings-as-errors.

Exceptions:

Documentation-only changes: check the diff, links, and consistency. Run relevant script checks if executable instructions or scripts changed.
Version-only root Directory.Build.props bump: verify that the task diff contains only the intended version change and that the commit prefix matches.

Finish

For authorized commit/push work, stage the task's explicit paths, inspect the staged diff, commit, then push to the verified remote and branch. Do not stage unrelated work with add .. Include related documentation in the same logical change.

Preserve configured hooks; fix hook failures and retry. Do not bypass hooks unless explicitly requested. Never create a branch or tag implicitly.

---name: git-workflowdescription: Commit, push, or version XerahS changes. Use only when the task includes these operations.---# Git and versioningFollow the wrapper and fallback guidance in [AGENTS.md](../../../AGENTS.md).## Version and commit format- Root `Directory.Build.props` supplies the app version. Before an app commit, compare it with the highest existing XerahS release tag; the version must be strictly greater. If needed, bump it to the next unreleased version.- App commits use `[vX.Y.Z] [Type] Concise description`, with types such as `Fix`, `Feature`, `Build`, `Docs`, or `Refactor`.- Shared-library/submodule commits, including `ShareX.ImageEditor`, use `[Type] Concise description` without the app version.- For requested version increments: fixes increment patch; features increment minor and reset patch; breaking changes increment major and reset minor/patch.- Do not put app versions in individual project files. Synchronize other tracked props only if they intentionally carry the XerahS app version; do not overwrite independent library versions.- Release automation synchronizes derived Chocolatey metadata and validates the generated package.## Verification and integrationInspect status, the task diff, tracking branch, and submodule state before staging. Preserve unrelated edits. Pull/rebase or update submodules when integration requires it, after checking that local work will be preserved; do not unconditionally pull into a dirty checkout.Before pushing code or build configuration, run the desktop solution build required by `AGENTS.md` and relevant tests. Do not disable warnings-as-errors.Exceptions:- Documentation-only changes: check the diff, links, and consistency. Run relevant script checks if executable instructions or scripts changed.- Version-only root `Directory.Build.props` bump: verify that the task diff contains only the intended version change and that the commit prefix matches.## FinishFor authorized commit/push work, stage the task's explicit paths, inspect the staged diff, commit, then push to the verified remote and branch. Do not stage unrelated work with `add .`. Include related documentation in the same logical change.Preserve configured hooks; fix hook failures and retry. Do not bypass hooks unless explicitly requested. Never create a branch or tag implicitly.

Frequently asked questions

Git Workflow