athena-review

To run a code review without committing, the skill reads all changed files in your git working tree, evaluates them against quality, security, and design criteria, and applies fixes automatically. It operates safely without altering your commit history.

An automated security and compliance audit checks changed files for security vulnerabilities, coding standard violations, and design flaws. It performs linting, static checks, and generates structured, audit-ready reports to ensure your code meets compliance readiness.

You can integrate linting and static analysis by running a review workflow that automatically reads git-tracked changes and applies static checks. This skill surfaces style issues and applies fixes across the working tree before you commit.

Yes, you can get a second opinion on code changes during an automated review. The workflow supports an optional Codex second-opinion feature, providing an additional external perspective on your modifications when available.

Yes, the automated code review works across any repository with git-tracked changes. It reads the working tree directly, making it suitable for diverse projects as long as there are uncommitted changes to evaluate.

You should use an automated code review workflow when you need auditability, structured reporting, and compliance readiness after implementing changes. It efficiently handles repetitive linting and static checks, while manual checks remain better for subjective design decisions.