Results for “code-review”

Scopes code-review blast radius and detects architectural hotspots using Tree-sitter AST analysis and GraphRAG, with an MCP server for graph-based analysis.

Python code-quality anti-patterns and review checks: exception-hierarchy correctness, singleton identity comparison, narrow exception handling, wildcard-import avoidance, magic-number naming, and dead-local removal. Use when reviewing or self-reviewing Python code for correctness and readability defects that linters and reviewers should catch.

Reviews pull request diffs for correctness, security, maintainability, and test coverage, providing severity-ranked findings and a close-out recommendation.

Implements a code change on a feature branch, opens a single pull request to main, and runs a code review loop before handoff.

Address Codex review comments on an open PR, re-run thermo-nuclear-code-quality-review, sync with the base branch, and push the updates. Use after a Codex (or human) review has landed on a PR you opened — the skill resolves each comment in code, marks the GitHub review thread resolved, then rebases/merges any new base-branch commits before pushing.

Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy, flagging issues with easing, duration, performance, and accessibility.

Self-contained code review checklist — formatting, type safety, duplication, readable conditions, logic-out-of-UI, test coverage, comment quality. Adapts to whatever tooling the project actually has (skips Prettier/TypeScript/test-runner checks if unconfigured). Use before merging, after completing a feature, or any time you want a second pass on code quality. In Claude Code, prefer the official `code-review` skill or `pr-review-toolkit`/`feature-dev` code-reviewer agents instead — both are real, installed, and go deeper than this checklist. This copy exists for Codex/Cursor portability, where those agents aren't available.

Performs structured code reviews of git branches, tracking findings in a living document and optionally running deep architectural analysis with subagents.

Reviews and authors Cloudflare Workers code against production best practices, covering configuration, request handling, architecture, observability, code patterns, and security.

Delegate coding tasks such as feature building, refactoring, and PR reviews to OpenAI's Codex CLI, with support for background execution and parallel worktrees.

Reviews a codebase for structural smells and refactors them with provable safety, using micro commits and green-bar discipline.

Applies four disciplined mindsets—audit, debt, help, review—to cut complexity, track deferrals, surface reference, and catch over-engineering in codebases.

Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.

Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.

Reviews development plans for gaps, hidden assumptions, critical misses, and XP violations, then presents prioritized findings for confirmation.

Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

Gates a git branch before merge by running code review, security, test, and accessibility passes on the diff, then emits a single verdict.

Enforces modern, safe, and idiomatic C++ coding practices based on the C++ Core Guidelines for writing, reviewing, or refactoring C++ code.

Interact with GitLab via helper functions for merge requests, issues, pipelines, and code review comments.

Review the current branch's changes against the project's code style and

Restructure code while preserving behavior: confirm tests are green, refactor in small steps, keep tests green, review, and commit with a gated workflow.

Run a full pull request review and post review comments directly to the current branch's GitHub PR. Requires the gh CLI to be installed and a PR to already exist for the current branch. Use when you want review feedback posted to GitHub as PR comments. For local code review without posting to GitHub, use code-review instead. Does not write or update PR descriptions — use update-pr-description for that.

Review QML code for correctness, performance, and idiom using qmllint and Qt6 best practices.

Use when reviewing a branch, PR, or work-in-progress changes against standards and spec

PR 代码评审，检查安全漏洞、Bug 和代码质量。

Automates repeated rounds of Copilot code review on GitHub pull requests: triggers review, triages threads, dispatches parallel fix agents, commits, replies, and loops until convergence.

Enforces dense, correct, and idiomatic code on all coding tasks, minimizing code bloat and agent operation overhead.

Identifies common software anti-patterns in code and suggests refactoring solutions to improve code quality.

Pre-commit/ship code review: Codex default; optional Claude, Pi, Droid, Copilot, Cursor, or OpenCode.

Reviews code using pi CLI with read-only tools. Delegates the review to pi (dev/pi) with a structured review rubric, running in read-only mode to prevent accidental edits. By default reviews uncommitted working tree changes (git diff HEAD) with pi restricted to the read tool; explicit targets (--branch/--diff/@file/PR) or --explore widen pi to read,grep,find,ls. Use when the user asks to "review code with pi", "pi review", "have pi review", "let pi review", or invokes /pi:review.

Review local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist-driven process.

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues using a structured checklist and attack surface mapping.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Creates a GitHub pull request with an auto-generated summary, running mandatory pre-commit and code-quality review gates, plus optional deep-review subagents, and posts findings into the PR body.

Reviews local branch changes for bugs, security vulnerabilities, and code quality issues, using a structured checklist and verification process.

Guides code modifications by reading affected files first, matching existing style, and making minimal, safe changes.