بنقرة واحدة
super-ralph-hotfix
Stamp reverse process beads with fast-track hotfix question bank for urgent production fixes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Stamp reverse process beads with fast-track hotfix question bank for urgent production fixes
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Stamp reverse process beads with bug investigation question bank for root-cause analysis and fix planning
Stamp decompose process beads — spec → phased work beads with review passes, structural quality gates, and clean-room carry-through
Stamp reverse process beads with feature-specific question bank for deeper business and technical interrogation
Stamp reverse process beads with refactor question bank for architecture migration and behavioral preservation
Stamp reverse process beads — any input → clean-room spec via bead graph with deep study, draft, fresh-eyes reviews, and consolidation
استنادا إلى تصنيف SOC المهني
| name | super-ralph-hotfix |
| description | Stamp reverse process beads with fast-track hotfix question bank for urgent production fixes |
This skill composes with /super-ralph-reverse. It stamps the same bead graph (deep study → draft → 3 review passes → consolidation), but injects the hotfix-specific question bank into bead 1's study instructions.
Follow /super-ralph-reverse exactly, but when stamping Bead 1 (Deep Study of Source Material), replace the ## Question Bank section with the hotfix question bank below.
Everything else — the bead graph structure, dependency wiring, description templates, stamping procedure — is identical to /super-ralph-reverse.
Include this in bead 1's description under ## Question Bank:
## Question Bank
Use these fast-track hotfix questions to guide your study — minimal
interrogation for maximum speed on urgent fixes:
### Fast Intake (1-3 questions max)
1. What's broken? Symptoms, error messages, stack traces.
2. What's the impact? Production down? Data loss? User-facing? Workaround?
3. What's the fix? If known, confirm. If not, investigate and propose.
4. Is there a test for this code path? Quick check — note file:line if found.