code-review
Code Review
Structured code review with severity-labeled feedback. Discovers scope from git state, loads language-specific rules on demand.
When to Use
- Reviewing uncommitted or committed code changes
- Reviewing a GitHub PR
- MR review or quality check
- Establishing review standards
Project Conventions
Before reviewing, check if the project has a docs/CodeStyle.md file (or similar convention document). If present, load it and treat project-specific rules as overrides to the general rules below.
Review Process
Phase 1: Scope Discovery
More from olamedia/analytics-skills
analyze-project
Use when starting work on any project to produce or update living documentation (TechStack.md, ProjectStructure.md) that bootstraps context for any AI agent session. Run before any feature work, or periodically to keep docs current.
13humanizer
>-
12architect
>-
12goal-definition
Use when you have a raw idea or request and need to define a clear goal with success criteria before exploring solutions. Use when requirements are vague, when "what does done look like" is unclear, or when assumptions need surfacing.
11prd
Use when you have a chosen direction and need to formalize requirements into a Product Requirements Document. Use when user stories, acceptance criteria, and scope boundaries need to be written down before architecture or implementation.
10analyze
Use when you have a raw idea or request and want to run the full analytics pipeline automatically — from research through to an interlinked task list. Best for straightforward problems where the full pipeline can flow with minimal back-and-forth.
10