ShareX Workflow and Versioning

Standardizes Git commits/pushes and Directory.Build.props versioning for the XerraS repo.

309|15|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/ShareX/XerahS --skill sharex-workflow-and-versioning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ShareX Workflow and Versioning
Source: https://github.com/ShareX/XerahS/tree/main/.ai/skills/xerahs-workflow
Command: npx skills add https://github.com/ShareX/XerahS --skill sharex-workflow-and-versioning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow standardizes Git commit/push practices and enforces a single source of truth for versioning using Directory.Build.props across the repository, reducing drift and human error during releases.

Core Features & Use Cases

  • Centralized version source of truth via Directory.Build.props.
  • Pre-commit checks and guarded push workflow including submodule synchronization.
  • Consistent version bump rules for patch, minor, and major across the codebase.

Quick Start

Update the repository version files with the canonical rules, then commit and push the changes using the standardized message format.

Frequently Asked Questions about ShareX Workflow and Versioning

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

FAQPage Schema
How do I standardize Git versioning across a dotnet repository?

Enforce Directory.Build.props as the single source of truth for versioning across your dotnet repository to reduce drift and human error during builds and releases.

How do I manage Git submodule synchronization during a release workflow?

Manage Git submodule synchronization during a release workflow by using a guarded push process that enforces pre-commit checks and updates submodules for release-ready builds.

What is the best way to enforce consistent Git commit messages and version bumps?

Enforce consistent Git commit messages and version bumps by defining standard commit message rules and applying consistent version bump rules for patch, minor, and major changes across the codebase.

Does this workflow require Directory.Build.props for version bump rules?

Yes, this workflow requires Directory.Build.props to serve as the centralized version source of truth, dictating the version bump rules for patch, minor, and major releases across the repository.

Why does my Git pre-commit check fail during version updates?

Git pre-commit checks fail during version updates if your changes do not align with the canonical rules enforced by Directory.Build.props or if submodule synchronization is incomplete before pushing.