github-release

The github-release skill is an automated workflow designed to streamline the software release process for projects hosted on GitHub. It specifically targets developers and release managers who maintain versioned software and wish to eliminate the manual overhead of drafting release notes and preparing repository state. By enforcing conventional commit standards, the skill programmatically aggregates and categorizes changes since the last version tag, ensuring that stakeholders receive clear, structured communication regarding new features, bug fixes, and maintenance tasks.

• Automatically identifies the latest version tag using git refnames to determine the scope of changes.

• Parses git log outputs to categorize commits based on conventional prefixes like feat:, fix:, and chore:.

• Integrates with the /bump-version skill to verify and update version strings within project-specific configuration files like tauri.conf.json.

• Generates a templated markdown report that includes specific download links, summary sections, and a link to the full GitHub compare view.

• Executes secure version tagging and release creation via the GitHub CLI (gh), ensuring that CI/CD pipelines are triggered only after all changes are pushed and verified.

• Prerequisites: Ensure the gh CLI is authenticated and the local environment has access to the repository tags.

• Workflow: The agent performs a sequence of git operations, including retrieving tag history and logging commits, before performing a commit and push for the version bump.

• Data Input: Operates on git history and repository files; ensures consistency between local versioning and remote releases.

• Constraints: Requires strict conventional commit adherence for accurate categorization; should be executed before any automated build triggers to prevent CI/CD drift.