nacl-tl-release

Automate end-to-end software releases by merging PRs, validating CI, and publishing changelogs.

23|2|Updated Apr 10, 2026

Search Tags:#workflow #changelog #github #release #tagging #ci #yougile

Ready to run

npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nacl-tl-release
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-release
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end software release by merging PRs into main, validating CI, bumping version numbers, creating tags, and publishing changelog and release notes.

Core Features & Use Cases

Orchestrates PR merging into main according to configured git strategy (squash/merge/rebase) and monitors for conflicts
Waits for production CI to complete and reports status, with retry and failure handling
Determines and applies semantic version bumps (major/minor/patch) and updates changelogs
Creates Git tags and publishes GitHub releases with release notes
Notifies stakeholders via YouGile and can close or update task boards accordingly
Supports resumption via a persistent release-status file to recover from interruptions

Quick Start

Run /nacl-tl-release to start the end-to-end release pipeline.

Frequently Asked Questions about nacl-tl-release

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

FAQPage Schema

How do I automate GitHub release orchestration including PR merging and CI validation?▼

Automating GitHub release orchestration requires merging PRs into main, validating production CI, bumping semantic versions, creating Git tags, and publishing release notes. This pipeline orchestrates the entire process end-to-end while monitoring for conflicts.

What is the best way to automate semantic version bumps and changelog generation for continuous integration?▼

Automating semantic version bumps and changelog generation requires evaluating merged changes to determine major, minor, or patch increments. The pipeline applies the version bump and updates the changelog file automatically before creating Git tags and publishing GitHub releases.

Does this release pipeline support resuming if the CI workflow fails or gets interrupted midway?▼

Yes, the release pipeline supports resuming after interruptions by persisting progress in a release-status JSON file. This allows the orchestration to recover and continue the workflow from the last completed step without restarting the entire process.

Can I send release notifications to a YouGile task board when a GitHub deployment finishes?▼

Yes, you can send release notifications to a YouGile task board when a deployment finishes. The pipeline notifies stakeholders via YouGile and can automatically close or update task board items based on the final release status.

How do I handle Git merge conflicts during automated release tagging?▼

Handling Git merge conflicts during automated release tagging involves monitoring PR merges according to your configured Git strategy, such as squash, merge, or rebase. The pipeline detects conflicts during the merge phase and reports the status before proceeding.

Do I need specific configuration files to automate end-to-end software releases?▼

Yes, you need specific configuration files to automate end-to-end software releases. The pipeline relies on a changelog markdown file for release notes, a config YAML for deployment settings, and a release-status JSON file to persist progress across runs.