smithery/aztr0nutzs

netninja-release-packager

Build NET-NiNJA release artifacts for legacy (Qt5) and modern (Qt6) targets, with version stamping and portable packaging. Use when creating release builds, packaging instructions, or PyInstaller specs for Windows.

Installation

$ npx skills add smithery/aztr0nutzs --skill netninja-release-packager

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/aztr0nutzs.

npx skills add smithery/aztr0nutzs

Browse all from smithery/aztr0nutzs

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,492 B
  • docs SUMMARY.md 247 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Netninja Release Packager

Goal

Produce two release artifacts (legacy Qt5 and modern Qt6) with clear build commands, version stamping, and predictable runtime behavior.

Read First

  • VERSION for release tag
  • WINDOWSPACKAGESUMMARY.md, WINDOWSRELEASENOTES.md, INDEX_WINDOWS.md
  • INSTALLWINDOWS.md, QUICKSTARTWINDOWS.md
  • requirements.txt, requirementslegacy.txt, requirementswindows.txt
  • launchgui.bat, launchgui.ps1, create_shortcut.ps1

Workflow

  1. Define build targets:

- Legacy: PyQt5 + CPU-gated compatibility. - Modern: PyQt6 + full feature set.

  1. Ensure requirements are clean and pinned for each target. Keep Qt5 and Qt6 separate.
  2. If PyInstaller specs exist, reuse them; otherwise define consistent build commands for each target.
  3. Stamp versions from VERSION into output naming and release notes.
  4. Package artifacts with launchers and required assets. Avoid bundling unused docs or tools.
  5. Document a single canonical build command per target plus a quick verification step.

Output Expectations

  • Two named artifacts: legacy and modern.
  • Clear build instructions and versioned outputs.
  • Notes on runtime expectations and CPU gating behavior.