l3rowniecakez·l3rowniecakez/Claude_Skill/skills/redmine-deploy-prod/SKILL.md

redmine-deploy-prod

Skill0 starsChanged 26 days agoLicence not identifiedView on GitHub

Create a new Redmine RM notifying IT Deploy team of App details to prepare a Production deploy, OR add another program + Redmine Ref to an existing Deploy Production RM — always asks first which of the two this call is. Each program is either Delphi .exe (default, unchanged) or Web App (e.g. bot-web-register/bot-web-admin — lighter table, no DPR_FILE row, no .exe suffix, different APPROVED_TAG formula). New-RM path copies its Master Pattern exactly (Assignee always IT Application Admin, Environment always Production/PROD; Due Date is the actual scheduled Deploy date, not the RM creation date), asking which RM number it should be a subtask of, then asking the App type before asking each unknown template variable one at a time (App name, REPOSITORY, COMMIT_HASH, PROGRAM_PATH, DPR_FILE if Delphi, RELEASE_VERSION, deploy date, DB scripts, checklist sheet, Redmine refs, contact person). New-RM path also opens two fixed subtasks once (assigned to whoever called the skill, not IT Application Admin) — "01-Email ขออนุมัตินำขึ้น PROD" and "02-แนบผล UAT" — never repeated on later calls. Existing-RM path asks the existing RMs number, then checks if the named App is already listed in Section 1: if it IS, updates ONLY that program's COMMIT_HASH, RELEASE_VERSION, and (re-derived) APPROVED_TAG in both the RM description AND the linked Checklist Sheet's "Full Commit Hash"/"Approved Tag" columns (REPOSITORY/PROGRAM_PATH/DPR_FILE untouched); if it's a genuinely new App, asks its type then appends a new numbered program block to Section 1 and new bullet(s) to Section 4 Redmine Ref. Never re-creates the two approval subtasks on this path. Always ends by giving the RM link to check. Use when user says "/redmine-deploy-prod" or wants to แจ้ง Deploy Production ให้ IT Deploy.

• Sends data out