Tagged code-review

Check finished tasks and features against their requirements before merging

Review changes against repo coding standards and the original spec in parallel

Review Flutter and Dart code for widget, state, performance and accessibility issues

Review code changes from the current session for bugs and quality issues

Review llama.cpp diffs and PRs against project conventions and common pitfalls

Review diffs and pull requests across several quality axes before they merge

Review code for security, performance and maintainability problems

Review code changes with parallel reviewers, then triage the findings

Review Git diffs and pull requests line by line with the ocr CLI for code quality

Have the host agent run code reviews itself while OCR handles file and rule selection

Review code for security, performance and quality issues before merging

Review code for lint issues, style problems and convention gaps

Give constructive pull request feedback and set review standards for teams

Coordinate parallel code reviews and consolidate findings by severity

Review PostgreSQL code for JSONB, array, schema and Row Level Security issues

Review code against your project instructions and refactor what falls short

Review SQL for injection, access control, standards and anti-patterns across databases

Review PR changes for security, input validation and API compatibility issues

Review PR changes for business logic, edge cases and query correctness

Review PR changes for resource use, error recovery and scaling problems

Review code changes thoroughly for bugs, risks and style issues

Run a thorough code review checklist for function, security and speed

Give constructive code review feedback that shares knowledge across the team

Review code with Codex AI and generate a changelog entry automatically

Open pull requests with clear descriptions that follow code review guidelines

Write and review code with quality-first architecture principles for any project

Build or update a persistent code review graph that hooks keep current

Run a structured code review of changes using impact and blast-radius analysis

Review a PR or branch diff with full structural context and blast-radius analysis

Review code changes for correctness, style, tests and potential issues

Review pull requests against code quality standards and a style guide

Review code for performance bottlenecks and optimization opportunities

Review code against a security checklist to find vulnerabilities

Review pull requests in many languages for complexity, risk and smells

Turn a markdown code review with severity callouts into a two-column HTML page

Review code through documented philosophies of engineers like Torvalds and Carmack

Review pull request diffs for security issues and code quality

Review code changes or a pull request for bugs, security and performance

Review code for architecture, SOLID principles, testability and performance

Review code changes for real defects and refute false positives before reporting

Review a diff or pull request for bugs, regressions, missing tests and standards

Review code with feedback tailored to each developer profile from session state

Review code for bugs, security issues and performance problems

Review PR diffs and loop fix commits until GitHub or GitLab checks pass

Review changes in two stages: spec compliance first, then code quality

Review pull requests with a short list of concrete asks and a clear verdict

Review local diffs or GitHub pull requests for bugs, security gaps and missing tests

Review code changes for test coverage gaps, edge cases and regressions

Review diffs for bugs, injection flaws, N+1 queries and architecture problems