القائمة
Use when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/4gray/iptvnator --skill release-cutيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use when changing Stalker or Ministra routes, stores, catalog or series shapes, playback progress, favorites and recent items, EPG, or remote control.
Use when changing user-visible Angular UI in IPTVnator, especially channel rows or lists, EPG views, settings and playlist surfaces, selection states, shared portal components, or light/dark styling.
Use when a change may need a .changes note, the Release note gate fails, or deciding whether type: internal or no-release-note applies.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | release-cut |
| description | Use when preparing, cutting, tagging, publishing, or verifying an IPTVnator release or its release assets. |
The tag workflow authors the public GitHub body with
node tools/release/extract-changelog-section.mjs --public "${VERSION}".
Keep the full changelog, including internal notes, committed before tagging.
Work from clean, current master with the intended remote named explicitly.
Confirm package.json contains bare semver, the exact v<version> tag does not
exist locally or remotely, CI is green, and all notes validate.
pnpm run release:notes:validate
pnpm run i18n:check
package.json.version.pnpm run release:notes:changelog.pnpm run release:notes:blog and finish every editorial
field. Patch release: edit the existing vX-Y post; do not scaffold or
force-overwrite it.pnpm nx run electron-backend:build-e2e, then
pnpm run release:screenshots.node tools/release/build-release-notes.mjs --consume.The consume command is the destructive boundary: it deletes the direct note
files. Stage only release-owned files, including exact website post/assets and
git add -A -- .changes, then commit and create the exact tag.
git commit -m "chore(release): v0.24.0"
git tag v0.24.0
Push the named remote's master branch first, then push only the exact
v<version> tag as a second command. Never use broad git push --tags.
For remote upstream and version v0.25.1, run exactly:
git push upstream master
git push upstream v0.25.1
Master and v* pushes can publish Docker images. The tag build creates a draft
GitHub release. Verify authored text plus generated commits and all required
macOS, Windows, DEB, RPM, Pacman (.pacman/.pkg.tar.*), AppImage, Snap,
Flatpak, updater metadata, blockmaps, and
linux-frame-copy-runtime-sources.tar.xz.
After verification, manually publish the GitHub release. That publication
automatically verifies its Snap assets and uploads them to edge.
Installed-Snap smoke and candidate/stable promotion remain manual. Keep the
blog draft during artifact verification; publish it in a follow-up commit and
verify the website deployment.
Missing CHANGELOG section: regenerate, commit, delete the bad tag locally and remotely only after resolving its exact target, then retag. Never publish a draft until the source archive and Snap contract pass.
The .codex and .claude copies of this skill must remain byte-identical.