القائمة
Canonical Git, commit/push, and Directory.Build.props versioning workflow for XerahS. Use for any task that changes version numbers or requires commit/push.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use the local ShareX checkout as the source of truth for ShareX.ImageEditor, find the latest upstream commit that touches it, and port or sync the matching changes into the XerahS ShareX.ImageEditor submodule with path-aware diffing and build gates.
Orchestrate XerahS release flow in strict order: run maintenance prep first, update-changelog second (optional only if docs/CHANGELOG.md is intentionally absent), verify build, bump/commit/push/tag while syncing Chocolatey version metadata, monitor GitHub Actions every 2 minutes, ensure standard release notes content, then set pre-release by default (use explicit opt-out for stable). On failures, inspect logs, fix root cause, and retry with the next patch release.
Rules and workflows for updating docs/CHANGELOG.md, including version grouping, aggressive consolidation, and GitHub tag-linked release headings.
Repository maintenance preparation for XerahS. Use before release or changelog work to sync repositories, inspect submodule state, identify version/changelog needs, and hand off commit/push/version rules to git-workflow.
Bring src/mobile-experimental Avalonia/MAUI mobile apps to feature and behavior parity with src/mobile/ios while preserving native platform feel. Use when comparing the Swift iOS app against XerahS.Mobile.Ava, XerahS.Mobile.Maui, or the experimental iOS share extension, implementing parity gaps, or validating Android/iOS experimental mobile flows.
Bring src/mobile/android to feature and behavior parity with src/mobile/ios while keeping each app native. Use when comparing iOS Swift/SwiftUI/UIKit mobile behavior against Android Kotlin/Jetpack Compose behavior, implementing missing Android features, or validating parity with the Test Android Apps emulator QA workflow.
| name | ShareX Workflow and Versioning |
| description | Canonical Git, commit/push, and Directory.Build.props versioning workflow for XerahS. Use for any task that changes version numbers or requires commit/push. |
This file is the single source of truth for Git and versioning rules that involve:
Directory.Build.props updatesThis supersedes the retired docs/development/RELEASE_PROCESS.md.
Directory.Build.props file as the working XerahS app version source of truth..csproj files.Directory.Build.props in the repository that intentionally carries the XerahS app version so values match.build/windows/chocolatey/xerahs.nuspec, must be synchronized from the root version during release automation..nupkg, so release metadata under build/windows/chocolatey/ must stay automation-friendly.0.0.z rule: keep major/minor, increase z).Before committing and pushing:
git pull --recurse-submodules
git submodule update --init --recursive
dotnet build src/desktop/XerahS.sln
Only continue when build succeeds with 0 errors.
git add .
git commit -m "[vX.Y.Z] [Type] concise description"
git push
Directory.Build.props <Version> as [vX.Y.Z], but only after verifying that version is strictly greater than the highest existing XerahS git tag.Directory.Build.props first and then commit with that bumped version.[Fix], [Feature], [Build], [Docs], [Refactor].ShareX.ImageEditor): omit [vX.Y.Z]; use [Type] description per AGENTS.md..githooks active (git config core.hooksPath .githooks).--no-verify unless explicitly requested for emergency use.