Automated summary
This skill guides an urgent bug-fix workflow from reproduction to deployment verification.
Strengths
- Clear step-by-step structure designed for emergency situations.
- Emphasizes minimal changes and fast testing.
- Includes Git commands and automated checks.
- Comprehensive checklist to prevent oversight.
Limitations
- Does not handle complex merge conflicts.
- Assumes basic Git and CI tool proficiency.
- May be too rigid for fixes requiring broader changes.
Use this workflow when a critical production bug requires a quick, safe fix.
Do not use for non-urgent bugs, refactoring, or feature work.
Security analysis
CautionThe skill instructs the AI to use Bash for git operations, building, and PR creation, which are powerful but legitimate actions. No destructive or exfiltrating commands are present.
No concerns found
How this analysis is madeExamples
Critical bug: the login page crashes when the users array is empty. Need to do a hotfix immediately.Urgent: payment flow throws a null pointer error. Please run the hotfix workflow to fix it.Hotfix needed: the app breaks when the API returns an empty response. Execute the emergency bug fix process.name: pf-hotfix description: 긴급 버그 수정 플로우. "핫픽스", "긴급", "버그 수정" 요청 시 사용. allowed-tools: Read, Write, Bash, Glob, Grep
PF 핫픽스 플로우
$ARGUMENTS 긴급 버그를 빠르게 수정합니다.
핫픽스 플로우
1. 버그 재현 & 원인 파악 (10분 이내)
↓
2. 브랜치 생성
↓
3. 최소한의 수정
↓
4. 테스트
↓
5. PR 생성 & 머지
↓
6. 배포 확인
1단계: 버그 재현 & 원인 파악
정보 수집
- 어떤 페이지/기능에서 발생?
- 재현 단계?
- 에러 메시지?
- 콘솔/네트워크 에러?
- 언제부터 발생? (최근 배포 이후?)
빠른 디버깅
# 최근 커밋 확인
git log --oneline -10
# 최근 변경 파일 확인
git diff HEAD~5 --name-only
# 에러 관련 파일 검색
/search "에러메시지"
2단계: 브랜치 생성
# 핫픽스 브랜치
git checkout main
git pull
git checkout -b fix/이슈번호-간단설명
# 예시
git checkout -b fix/456-login-crash
3단계: 최소한의 수정
원칙
- 오직 버그만 수정 - 리팩토링 금지
- 영향 범위 최소화 - 관련 파일만 수정
- 테스트 가능한 수정 - 수정 후 바로 확인 가능
수정 예시
// ❌ 핫픽스에서 하면 안 되는 것
// - 코드 정리
// - 변수명 변경
// - 구조 개선
// ✅ 핫픽스에서 해야 하는 것
// - 버그의 직접적인 원인만 수정
// Before (버그)
const user = users[0];
console.log(user.name); // users가 빈 배열이면 에러
// After (수정)
const user = users[0];
if (user) {
console.log(user.name);
}
4단계: 테스트
필수 확인
# 1. 타입 체크
pnpm tsc --noEmit
# 2. 린트
pnpm lint
# 3. 빌드
pnpm build
# 4. 로컬에서 버그 재현 테스트
pnpm --filter 앱이름 dev
체크리스트
- [ ] 버그가 수정되었는가?
- [ ] 다른 기능이 깨지지 않았는가?
- [ ] 빌드가 성공하는가?
5단계: PR 생성 & 머지
커밋
git add .
git commit -m "fix: 로그인 페이지 크래시 수정
- users 배열이 빈 경우 null 체크 추가
- Fixes #456"
PR 생성
git push -u origin fix/456-login-crash
gh pr create --title "fix: 로그인 페이지 크래시 수정" --body "
## 버그
로그인 페이지에서 users 배열이 빈 경우 크래시 발생
## 원인
users[0] 접근 시 null 체크 누락
## 수정
null 체크 추가
## 테스트
- [x] 로컬 빌드 성공
- [x] 버그 재현 후 수정 확인
Fixes #456
"
빠른 머지 요청
- 리뷰어에게 긴급 리뷰 요청
- 또는 권한이 있다면 셀프 머지 (긴급 시)
6단계: 배포 확인
자동 배포 (main 머지 시)
# GitHub Actions 상태 확인
gh run list --limit 5
# 또는 GitHub에서 확인
# Actions 탭 > deploy-staging 워크플로우
수동 확인
# 스테이징 서버에서 버그 수정 확인
# 프로덕션 배포 후 최종 확인
핫픽스 체크리스트
[ ] 버그 원인 파악됨
[ ] 최소한의 변경만 수행
[ ] 타입 체크 통과
[ ] 린트 통과
[ ] 빌드 성공
[ ] 버그 수정 확인
[ ] 사이드 이펙트 없음
[ ] PR 생성
[ ] 배포 확인
긴급 연락
- 배포 실패 시: DevOps 담당자
- 서버 에러 시: 백엔드 담당자
- DB 문제 시: DBA
롤백 (최후의 수단)
# 이전 커밋으로 롤백
git revert HEAD
git push
# 또는 이전 배포 버전으로 롤백 (서버에서)
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/hotfix-flow-mm78nngn/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/hotfix-flow-mm78nngn' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/hotfix-flow-mm78nngn/download' --output '.skill-downloads/hotfix-flow-mm78nngn/SKILL.md.part' && mv '.skill-downloads/hotfix-flow-mm78nngn/SKILL.md.part' '.skill-downloads/hotfix-flow-mm78nngn/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Write, Bash, Glob, Grep
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/hotfix-flow-mm78nngn/SKILL.md' && test -s '.skill-downloads/hotfix-flow-mm78nngn/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pf-hotfix' && cp -R '.skill-downloads/hotfix-flow-mm78nngn' '.claude/skills/pf-hotfix'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/hotfix-flow-mm78nngn'openskills read 'hotfix-flow-mm78nngn'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/hotfix-flow-mm78nngn/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.