القائمة
Tag and push a release. Use when the user says "release X.Y.Z". Does NOT merge any branches — just tags the current HEAD and pushes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Code-sign the MAGDA Windows installer with the Certum cloud certificate (SimplySign). Use when releasing on Windows, when the signing job in release.yml needs attention, or when troubleshooting "cert not found" / SmartScreen warnings.
Work on MAGDA's compiled Faust devices (synths/FX whose DSP is a .dsp file compiled to C++ at build time). Use when adding or changing a parameter on a compiled Faust plugin (e.g. Poly Synth, the filter engines, compiled FX), creating a new compiled Faust device, or wiring its custom UI. Covers the .dsp -> generated.cpp pipeline, the host-slot contract, and UI/linking.
Update the MAGDA application icon (dock / taskbar / window icon) from a new source PNG. Use when the user wants to change, swap, or update the app icon, e.g. "update the app icon to Bold-M6". Covers the assets/app_icon.png pipeline, the square-PNG requirement, and rebuilding so JUCE regenerates the .icns/.ico.
Manage MAGDA translations via Crowdin - how to add source strings, push sources, push a specific locale's translation via CLI, and the rules about who writes what.
Write values from MAGDA into a te::AutomatableParameter (slider moves, controller input, state restore, modifier sync). Covers the setParameterFromHost requirement, why setParameter silently drops host writes when modifiers are active, and what to do after a TE submodule bump. Use when adding a new DeviceProcessor, wiring a new control surface, debugging "slider does nothing when an LFO/macro is on the parameter", or rebasing the TE patch.
Analyze MAGDA crash logs and Windows minidumps. Use when the user reports a crash, provides a crash log or .dmp file, or asks to investigate a crash.
| name | release |
| description | Tag and push a release. Use when the user says "release X.Y.Z". Does NOT merge any branches — just tags the current HEAD and pushes. |
| user_invocable | true |
| argument | version (e.g. 0.2.2 or 0.5.3-rc0) |
A release is only a git tag. It does NOT involve merging feature branches.
0.2.2, 1.0.0) MUST be tagged on main.-rc, -alpha, -beta, -pre) MAY be tagged on any branch — useful for cutting an RC off a feature branch before it merges.A version is a pre-release if it contains a hyphen followed by rc, alpha, beta, or pre (e.g. 0.5.3-rc0, 1.0.0-beta.2).
main, and main must be up to date with origin/main.Stable release:
git checkout main
git pull origin main
git tag v<VERSION>
git push origin v<VERSION>
Pre-release (RC/alpha/beta) from current branch:
# Verify branch is clean and pushed
git status
git push # ensure remote is up to date
git tag v<VERSION>
git push origin v<VERSION>
v in the tag (e.g. v0.2.2, v0.5.3-rc0).v prefix already, don't double it.