latitude-release-discipline

Name: latitude-release-discipline
Availability: InStock
Author: joolbits

Validate branch, version, build, and tag alignment before software releases.

Updated Jan 29, 2026

Search Tags:#automation #git #versioning #build #release #guardrails

Ready to run

npx skills add https://github.com/joolbits/latitude --skill latitude-release-discipline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: latitude-release-discipline
Source: https://github.com/joolbits/latitude/tree/main/.windsurf/skills/latitude-release-discipline
Command: npx skills add https://github.com/joolbits/latitude --skill latitude-release-discipline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents costly mistakes during the software release process by enforcing a strict checklist and guarding against common errors like building from the wrong branch or shipping debug artifacts.

Core Features & Use Cases

Branch and Version Validation: Ensures releases are made from the correct branches with matching version strings.
Build Integrity Checks: Verifies that builds are clean, successful, and do not contain unintended artifacts.
Tagging and Uploading Discipline: Guides the correct tagging of commits and the proper uploading of release files.
Use Case: A developer needs to release a new version of the Latitude mod. This Skill will guide them through checking out the correct branch, verifying the version number in gradle.properties, performing a clean build, inspecting the resulting JAR, and finally, creating and pushing the correct Git tag.

Quick Start

Use the latitude-release-discipline skill to ensure your current branch and working tree are clean before proceeding with a build.

Frequently Asked Questions about latitude-release-discipline

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

FAQPage Schema

How do I enforce release guardrails to prevent incorrect builds and tags in Git?▼

Release guardrails prevent incorrect builds and tags by validating working tree cleanliness, correct branch checkout, accurate version strings, successful clean builds, and tag-to-commit alignment before publishing.

What is release discipline in software versioning and why is it needed?▼

Release discipline is a strict validation process for software versioning needed to prevent costly mistakes like building from wrong branches, shipping debug artifacts, or mismatching version strings in build configurations.

Can I use automated release checks to verify version strings in gradle.properties before building?▼

Automated release checks can verify version strings in gradle.properties by comparing the expected version against the actual property value, ensuring the build output matches the intended release version before proceeding.

What's the best way to ensure a clean Git working tree before starting a software release?▼

The best way to ensure a clean Git working tree before a release is to enforce a checklist that validates branch checkout, verifies no uncommitted changes, and confirms the working directory is ready for a clean build.

Why does my release build fail when the Git tag is misaligned with the target commit?▼

Release builds fail on tag misalignment because release guardrails validate that the Git tag accurately points to the exact commit used for the build, preventing incorrect or orphaned release artifacts from being uploaded.

How do I validate jar artifacts before uploading a software release?▼

Validating jar artifacts before a release involves checking the successful clean build output to ensure the jar contains the correct version and no unintended debug artifacts, safeguarding against shipping incorrect files.