risk-register
Risk Register
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.
When to Use
Use this skill when your change involves:
- Authentication/Authorization - Login, sessions, permissions, tokens
- User Data - PII, passwords, payment info, user content
- Data Migrations - Schema changes, data transformations, backfills
- External Integrations - Third-party APIs, webhooks, OAuth
- Infrastructure - Deployment, scaling, configuration changes
- Breaking Changes - API changes, behavioral changes, deprecations
Quick Start
/risk-register
More from zbruhnke/claude-code-starter
explain-code
Explain how code works in detail. Use when trying to understand unfamiliar code, complex logic, or system architecture.
193refactor-code
Refactor code to improve clarity and maintainability without changing behavior. Use when improving readability, reducing complexity, or eliminating duplication.
20code-review
Review code changes for quality, security, and best practices. Use when reviewing staged changes, pull requests, or specific files before merging.
12wiggum
Start an autonomous implementation loop from a spec or PRD. Enters plan mode for user approval, enforces command gates (test/lint/typecheck/build), validates dependencies, commits incrementally, and maintains documentation and changelog. Production-ready quality gates.
8generate-tests
Generate comprehensive tests for code. Use when adding test coverage, implementing TDD, or ensuring code reliability.
8review-mr
Review a merge request or branch. Compares a branch against main/master, summarizes changes, highlights concerns, and provides actionable feedback. Use for PR reviews or before merging.
8