skills.rest
sensei-hacker
sensei-hackerCOMMUNITY
Explore all skills by this author →
𝕏@sensei_hackerGitHub

upload-release-assets

Upload firmware hex files and configurator packages to GitHub releases via gh.

4|2|Updated Nov 30, 2025
Search Tags:#automation#GitHub#release#firmware#assets#upload#configurator
One-click install
npx skills add https://github.com/sensei-hacker/inav-claude --skill upload-release-assets
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: upload-release-assets
Source: https://github.com/sensei-hacker/inav-claude/tree/main/.claude/skills/upload-release-assets
Command: npx skills add https://github.com/sensei-hacker/inav-claude --skill upload-release-assets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the time-consuming and error-prone process of uploading numerous firmware hex files and configurator packages to a GitHub release, ensuring consistency and accuracy.

Core Features & Use Cases

  • Automated Renaming: Rename firmware files from CI build formats to official release naming conventions.
  • Bulk Upload: Upload all specified files from a source directory to a GitHub release tag.
  • Upload Verification: Confirm the number of assets uploaded matches expectations.
  • Use Case: A release manager has prepared all final firmware and configurator builds for INAV 9.0.0-RC2 and needs to upload them to the official GitHub release, ensuring correct file names and a complete set.

Quick Start

Upload all firmware hex files from 'claude/release-manager/downloads/9.0.0-rc2' to the INAV 9.0.0-RC2 release.

Frequently Asked Questions about upload-release-assets

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

FAQPage Schema
How do I automate uploading firmware files to a GitHub release?▼

Automate firmware uploads by preparing hex files in a source directory, then use this Skill to rename them to release conventions and upload all assets to your GitHub release tag via gh. The Skill verifies the upload count matches expectations.

Can I rename firmware files during upload to GitHub?▼

Yes. The Skill automatically renames firmware files from CI build formats to official release naming conventions as part of the upload process, ensuring consistency across releases.

What's the best way to upload multiple configurator packages and firmware hex files together?▼

Bulk upload all files from a single source directory to a GitHub release in one operation. The Skill handles per-platform configurator packaging and firmware hex files together, then confirms asset count accuracy.

Does this work with release candidates and nightly builds?▼

Yes. The Skill supports iNavFlight firmware and configurator releases including RC versions, final releases, and nightly-build renaming with appropriate file normalization for each type.

Can I overwrite existing assets when uploading to a GitHub release?▼

Yes. The Skill supports optional clobber functionality to overwrite existing assets during upload, useful when re-releasing with corrected files.

What happens if the number of uploaded assets doesn't match what I expected?▼

Post-upload verification confirms the asset count matches expectations. If counts don't align, you can identify missing or extra files before finalizing the release.

Related Skills

Explore More Software Engineering Skills→
sensei-hackersensei-hacker
4

download-release-artifacts

Downloads firmware hex files and configurator builds for a specified INAV release via GitHub CLI.

Community
Intermediate
CyanAutomationCyanAutomation
1

release-publish

Automate tag-triggered Docker image and GitHub release publication.

Community
Advanced
rudironsonirudironsoni

dotnet-cli-release-pipeline

Automate .NET CLI releases with cross-platform builds and package manager distribution.

Community
Advanced
jtenniswoodjtenniswood
219

release

Create and verify GitHub releases with semantic version tags and asset uploads.

Community
Advanced