JavaScript/ES6+ coding standards following Airbnb guidelines, modern patterns, React best practices, and comprehensive Jest testing. Use for JavaScript projects requiring clean, maintainable, production-ready code with modern tooling.
Final code/plan review using Codex. Use as the last review step after sonnet and opus.
When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.
Review a pull request for correctness, regressions, and missing tests. Use when a mid-level developer needs structured review guidance.
Analyze code complexity metrics including cyclomatic complexity and nesting depth. Use to identify code that needs refactoring.
Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.
Scan code for security vulnerabilities and unsafe patterns. Use before committing sensitive code or in security reviews.
Validate type safety in Mojo code including parametric types and trait constraints. Use during code review or when type errors occur.
Validate Mojo syntax against current v0.26.1+ standards. Use to catch syntax errors before compilation.
Run comprehensive security vulnerability scans when reviewing code. Automatically uses basic mode (fast, high/medium severity only) for first reviews, advanced mode (comprehensive, all severities) for iterations. Detects SQL injection, XSS, hardcoded secrets, insecure dependencies. Use before approving any code changes or pull requests.
Format Mojo code using mojo format command. Use when preparing code for commit or when formatting checks fail.
Check function inputs for correctness and safety. Use when implementing defensive programming.
Run pre-commit hooks locally or in CI to validate code quality before committing. Use to ensure commits meet quality standards and CI will pass.
Diagnose and fix Nix evaluation errors, build failures, and module conflicts.
Validate Mojo code patterns (out self, mut, List, etc.) against best practices. Use to ensure code follows project standards.
Scan code or configuration for common security issues. Use when a mid-level developer needs a quick security pass.
Run all configured linters including mojo format, markdownlint, and pre-commit hooks. Use before committing code to ensure quality standards are met.
Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.
Complete workflow for conducting thorough code reviews with structured feedback
Validate agent YAML frontmatter and configuration. Use before committing agent changes or in CI.
Validate documentation structure, check for missing sections, verify markdown syntax, ensure consistency with templates. Use when user mentions docs validation, structure check, README review, documentation quality, or wants to verify documentation completeness.
