skills.rest
chshzh
chshzhCOMMUNITY
Explore all skills by this author →
GitHub

chsh-sk-ncs-git-release

Automates git tagging, CI monitoring, and GitHub Release publishing for NCS firmware projects.

1|Updated Jan 30, 2026
Search Tags:#release automation#gh cli#github release#ci monitoring#git tag#ncs firmware#hex artifact
One-click install
npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-git-release-chshzh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: chsh-sk-ncs-git-release
Source: https://github.com/chshzh/claude/tree/main/skills/chsh-sk-ncs-git-release
Command: npx skills add https://github.com/chshzh/claude --skill chsh-sk-ncs-git-release-chshzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing NCS firmware involves a fragile chain of git tagging, GitHub Actions CI, artifact naming, and release publishing where one misstep produces broken or missing .hex artifacts. This Skill provides a repeatable, verified release workflow with built-in failure recovery. ## Core Features & Use Cases - Release Tagging: Decide between version tags, patch bumps, rolling releases, and pre-releases, then create and push annotated git tags. - CI Monitoring & Debugging: Watch GitHub Actions runs with gh CLI, inspect failed step logs, and apply fixes from a table of common CI failures. - Release Publishing: Create or update GitHub Releases, upload .hex firmware artifacts, and manage stale assets. - Use Case: After finishing a feature on an nRF Connect SDK project, tag v1.2.0, watch the CI build, and publish the merged.hex artifact to a GitHub Release without manually juggling gh commands. ## Quick Start Ask Claude to tag a new release for your NCS app and watch the CI run until the firmware artifact is published to GitHub.

Frequently Asked Questions about chsh-sk-ncs-git-release

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

FAQPage Schema
How do I tag and publish a firmware release on GitHub?▼

Create an annotated git tag with git tag -a v<version> -m, push it, then monitor the GitHub Actions run with gh run watch. If CI does not auto-release, use gh release create with the built .hex artifact attached.

How do I watch GitHub Actions CI runs from the command line?▼

Use gh run list to see recent runs and gh run watch <run-id> --interval 30 for live updates. On failure, run gh run view <run-id> --log-failed to get the failing step logs.

Why does my GitHub Actions firmware build fail with merged.hex not found?▼

The merged.hex file is only produced when MCUboot sysbuild is enabled. Fall back to zephyr/zephyr.hex or check your sysbuild.conf configuration to enable the merged output.

Should I re-tag when a release CI run fails?▼

No. Fix the underlying issue, push the commit, and watch the new run. Only re-tag if the previous tag itself was wrong, since re-tagging creates confusion about which commit a version points to.

When should I use a rolling release instead of a version tag?▼

Use a rolling release for nightly or continuous builds by pushing to main and letting CI overwrite the latest release. Use annotated version tags for stable feature releases, bug fixes, and pre-releases like v1.2.0-rc1.

Related Skills

Explore More Software Engineering Skills→
chshzhchshzh

ncs-env-setup

Configure and validate the Nordic nRF Connect SDK environment for west workflows.

Community
Advanced
JORDAN0615JORDAN0615

jetson-validate-image

Validate deployed Jetson BSP images via static artifact checks and on-target tests.

Community
Intermediate
AcigapAcigap

github-actions-failure-debugging

Diagnose failed GitHub Actions workflows for ESP32 firmware builds.

Community
Intermediate
adamfilliadamfilli
11

release

Automate version bumps, commits, and GitHub releases for software projects.

Community
Intermediate