Triage P1 and P2 bugs and generate a markdown day-one patch plan.
npx skills add https://github.com/nevesb/idol-agency-maker --skill day-one-patch-nevesb
Please help me install this Agent Skill. Skill: day-one-patch Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/day-one-patch Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill day-one-patch-nevesb
Launch windows are high risk and post-gold issues can cause chaos if not scoped and gated correctly. This Skill prevents scope creep, ensures fixes are safe and fast, enforces a rollback plan, and provides a lightweight QA gate so teams can ship a focused day-one patch with minimized risk.
Prepare a day-one patch plan that prioritizes safe P1 and P2 fixes from production/qa/bugs, produce a rollback plan, and write the patch record to production/releases/day-one-patch-[version].md.
High-intent search queries and answers about installing and using this skill.
To scope a safe day-one patch, you triage P1 and P2 bugs from cert feedback, enforce a four-hour per fix limit, coordinate with lead programmers and QA, and require a predeployment rollback plan before shipping.
A day-one patch is a focused post-gold master update that fixes urgent issues surfaced by cert feedback or late playtests. You need to prepare one during the release or polish stage to address critical bugs before launch.
Prevent scope creep during post-gold bug triage by classifying open bugs by severity, filtering for fixes estimated under four hours, and enforcing a strict QA gate with rollback checks before any deployment.
Configuration-only fixes are handled directly within the day-one patch plan, while code changes require spawning focused implementation tasks coordinated with lead-programmer and qa-tester agents for verification.
Day-one patch deployment requires a formal release-manager rollback plan prepared before changes, followed by targeted smoke checks or broader regression testing to ensure safe shipping and QA sign-off.
The four hour per fix limit restricts day-one patches to safe, rapid fixes only, meaning complex bugs exceeding this threshold or requiring broad regression are deferred to prevent launch window risk.
olaservoFetch all open GitHub issues via pagination and generate a triage report.
scomofoSelect P1/P2 fixes for a safe day-one patch with rollback planning and QA gating.
wanghaishengCreate hotfix branches with approval tracking and backporting for S1/S2 bugs.
polseguScope, prioritize, implement, and QA-gate urgent post-gold-master game fixes.
