deep-review
Deep Review
Perform thorough code review using three perspectives with opposing mindsets. Their disagreement surfaces issues; their agreement signals confidence.
When to Use
- Architectural changes, multi-file refactors, or security-sensitive code
- PRs that are too important for single-pass review
- When you suspect confirmation bias in a standard review
- High-stakes merges where the cost of a missed issue is high
When NOT to Use
- Routine single-file edits (use standard
code-reviewskill) - Documentation-only PRs
- Formatting/linting changes
More from fabioc-aloha/alex_skill_mall
refactor
Systematic code refactoring to improve maintainability without changing behavior. Use when asked to "refactor this", "clean up this code", "improve code quality", "simplify this", "reduce complexity", or "eliminate code smells". Always preserves existing behavior.
1socratic-questioning
Help users discover answers, don't just deliver them.
1graphic-design
Patterns for visual design, SVG creation, layout composition, typography, and brand identity.
1data-preparation
Data cleaning, profiling, transformation, and quality gates -- prepares raw data for visualization and analysis
1dashboard-design
Dashboard layout patterns, KPI card design, filter architecture, narrative flow through panels, and self-contained HTML generation
1ui-ux-design
User interface design, user experience optimization, accessibility compliance, design systems
1