risk-register

SKILL.md

For changes that touch sensitive areas (authentication, data, migrations, infrastructure), document the risks explicitly. This is what senior developers do naturally - making it explicit ensures nothing is overlooked.

| Session hijacking | Critical | Secure cookies, HTTPS, token rotation | | Credential stuffing | High | Rate limiting, MFA, breach detection | | Token leakage | Critical | Short expiry, secure storage, no logging | | Privilege escalation | Critical | Strict authz checks, principle of least privilege |

| Account takeover | Critical | Email verification, suspicious activity alerts |

인증, 데이터 또는 마이그레이션과 관련된 변경에 대한 위험을 문서화합니다. 주요 위험, 테스트/모니터링 방법, 롤백 전략을 나열합니다. 출처: zbruhnke/claude-code-starter.

원본 보기