skills.rest
Rammer-Tech
Rammer-TechOFFICIAL
Explore all skills by this author →
WebsiteGitHub

publish-release

Automate RoEFactura releases by scanning commits, drafting CHANGELOGs, and publishing NuGet packages.

1|Updated Jun 18, 2025
Search Tags:#automation#git#workflow#release#semver#nuget#CHANGELOG
One-click install
npx skills add https://github.com/Rammer-Tech/ro-efactura --skill publish-release-rammer-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: publish-release
Source: https://github.com/Rammer-Tech/ro-efactura/tree/main/.cursor/skills/publish-release
Command: npx skills add https://github.com/Rammer-Tech/ro-efactura --skill publish-release-rammer-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates RoEFactura releases by analyzing commits vs main, inferring semver bumps, drafting CHANGELOG entries, and executing packaging and publishing steps after a single user approval.

Core Features & Use Cases

  • Infer the appropriate semantic version bump by scanning commits on origin/main..HEAD and applying conventional-commit rules.
  • Draft and organize CHANGELOG notes under an Unreleased section for the upcoming release.
  • After user approval, automatically create release branches, bump the version, build and pack NuGet packages, and optionally tag and publish GitHub releases.

Quick Start

Trigger the RoEFactura release workflow and approve the plan when prompted.

Frequently Asked Questions about publish-release

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

FAQPage Schema
How do I automate semantic versioning and NuGet releases from commit history?▼

Automate semantic versioning by scanning commits between origin/main and HEAD to infer the correct semver bump, draft CHANGELOG entries, and push NuGet packages after a single approval.

How does conventional commit scanning determine the correct version bump?▼

Conventional commit scanning analyzes commit history against origin/main..HEAD, applying rules to infer whether the next semantic version requires a major, minor, or patch bump.

Can I draft a CHANGELOG and publish a GitHub release in one workflow?▼

You can draft CHANGELOG entries under an Unreleased section and optionally tag and publish GitHub releases automatically after approving the packaging and publishing plan.

Do I need to manually approve each packaging and publishing step during the release?▼

No, the workflow executes release branch creation, version bumping, NuGet packaging, and GitHub publishing after a single user approval, preventing multiple prompts during the process.

What pre-flight checks are included to ensure reproducible release automation?▼

Release automation includes pre-flight checks and guardrails with auditable steps to ensure reproducibility and prevent errors before executing the end-to-end packaging workflow.

Related Skills

Explore More Software Engineering Skills→
sendbird-playgroundsendbird-playground
3

stave-release

Automate versioned release PR creation for the Stave repository.

Official
Advanced
learnzdevelopmenthublearnzdevelopmenthub
1

dev-release

Automate release branches, tests, changelogs, and GitHub releases.

Community
Advanced
julianobarbosajulianobarbosa
7

Git

Automate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.

Community
Advanced
chrislyonschrislyons

git.release.prep

Automates release prep with semantic versioning, changelog generation, and GitHub publishing.

Community
Intermediate