Create emergency hotfix branches from main for critical production issues.
npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-hotfix
Please help me install this Agent Skill. Skill: dev-hotfix Source: https://github.com/learnzdevelopmenthub/paadhai/tree/main/.claude/skills/dev-hotfix Command: npx skills add https://github.com/learnzdevelopmenthub/paadhai --skill dev-hotfix
This skill guides urgent production fixes so you can stop regression impact without waiting for the normal development pipeline, reducing downtime after critical incidents.
Invoke /dev-hotfix, describe the production outage, confirm the severity gate prompts, and follow the guided steps to patch main quickly.
High-intent search queries and answers about installing and using this skill.
To create an emergency hotfix branch from main, you invoke the guided workflow, provide the production issue description, and pass the severity assessment gate before branching. This process bypasses the normal develop cycle to patch main quickly and stop regression impact.
The hotfix workflow enforces regulated verification by loading build, lint, and test commands from .paadhai.json. It runs these commands and requires successful results before committing, ensuring the emergency fix does not introduce new failures to main.
The best way to bypass the normal cycle during a critical production outage is using an emergency hotfix workflow. It orchestrates issue intake, severity checks, and explicit confirmation gates to create a fix branch directly off main, reducing downtime after incidents.
Yes, you need a .paadhai.json configuration file to run CI verification during a hotfix. The workflow loads your build, lint, and test commands directly from this file, enforcing successful execution before it allows committing changes to the hotfix branch.
Yes, you can automate the git commit and PR procedure for production hotfixes. After verification passes, the workflow commits to the hotfix branch, opens a PR to main, polls CI status, and outlines back-merge and release next steps for the team.
You should avoid using an emergency hotfix workflow for non-critical production issues. It is designed specifically for severe incidents requiring immediate mitigation, meaning you should rely on the normal development pipeline for routine fixes to prevent bypassing established review cycles.
akiojinCreate a hotfix branch, guide fixes, open a pull request to main, and confirm patch releases.
RooseveltAdvisorsDetect the current development stage and enforce CI/CD pipeline adherence.
algorithmbasicsMerge a PR, wait for CI, deploy to production, and verify canary health.
ohyesgocoolMerge target branch changes into a feature branch with conflict resolution and verification.
