Results for “code review”

Review code changes for correctness, completeness, bugs, edge cases, and quality. Load when the user explicitly asks to review code, check a PR, review a diff, audit recent changes, or verify an implementation matches requirements. Also triggers on "review this code", "check this PR", "review my changes", "code review", "did this implement correctly", "audit this diff", or any explicit request for a formal code review. Do NOT load for "review changes for context" or "review what happened" — those are requests to read code, not to perform a formal review.

The English summary is being prepared. Showing the original description.

Review code using shared OpenClaw instructions and a Python helper, while also following the target repository’s review requirements. This skill points to a common installation that supplies the actual review procedure.

• Reviewing code with shared OpenClaw instructions
• Applying repository-specific review requirements
• Keeping shared review instructions up to date

Compose compact, structured prompts for coding, debugging, review, and research with Codex or GPT-5.4. This internal skill defines task scope, completion criteria, output format, verification steps, and evidence requirements using consistent XML tags.

• Define implementation scope and completion criteria
• Include verification steps in debugging requests
• Specify evidence requirements for code reviews

Use the P7 engineering workflow in Codex CLI through a command alias. It guides planning, implementation, and a three-question self-review, then requires command and output evidence before reporting completion.

• Calling the P7 workflow from Codex CLI
• Planning, implementing, and reviewing a coding task
• Reporting completion with command and output evidence

Have Gemini critically review research developed with Codex. Multiple rounds of discussion examine logical gaps, missing experiments, and narrative weaknesses, then turn the findings into experiment plans, paper outlines, and documented research priorities.

• Get Gemini feedback on research developed with Codex
• Identify logical gaps and missing experiments
• Develop a paper outline through review discussions

Run Polly AI Review and Open Code Review repeatedly on a pull request. Track each finding, fix relevant issues, document justified dismissals, and verify that review evidence and recorded decisions cover the latest commit.

• Resolving findings from two automated PR reviewers
• Reviewing each new commit after fixes
• Recording evidence for dismissed or duplicate findings

Review code using shared OpenClaw instructions and a Python helper, while also following the target repository’s review requirements. This skill points to a common installation that supplies the actual review procedure.

• Reviewing code with shared OpenClaw instructions
• Applying repository-specific review requirements
• Keeping shared review instructions up to date

Prepare a codebase for an external security review by defining goals, running static checks, improving test coverage, and removing unused code. Assemble the review scope, verified build instructions, diagrams, and documentation into a package for auditors.

• Preparing a codebase for an external security audit
• Organizing fixes and missing tests before review
• Defining the review scope and a stable code version

Audit Claude Code and Codex hooks, actions triggered by agent events. Check commands, trigger conditions, blocking behavior, and timeouts to identify why hooks fail to run, fail to block actions, or delay the agent.

• Validate hook settings before committing
• Investigate hooks that never run
• Check policy hooks that fail to block actions

Review code changes and connected code for bugs, security risks, load problems, missing tests, slowdowns, and unnecessary complexity. Get prioritized findings with concrete failure scenarios, small fixes, and the consequences of leaving each issue unresolved.

• Review a pull request or the latest commit
• Check for security and data loss risks
• Find failures under expected load and gaps in tests

Review estimated spending, token usage, and cache hit ratios across Claude Code, Codex, and Grok using local logs. Filter by time, project, or provider, while keeping currencies separate and identifying models without pricing.

• Reviewing estimated spending for the past seven days
• Comparing usage across providers and models
• Checking costs for a specific project or time range

Review changes since the last npm release through parallel change analysis, hands-on quality checks, and an overall release assessment. Receive a readiness verdict, blocking issues, version recommendations, and a draft changelog with compatibility concerns.

• Assess readiness before an npm release
• Check breaking changes and migration needs
• Review version bump recommendations

Display a preset introduction to Oh My OpenCode through an Easter egg command. The message outlines the plugin’s agent coordination, code navigation, structural search, built-in search integrations, and compatibility with Claude Code configuration.

• Reading a brief introduction to Oh My OpenCode
• Trying the hidden command
• Reviewing the plugin features listed in its introduction

Diagnose problems in Muse Code itself using the installed executable, settings, crash reports, and session evidence. The skill narrows down the likely failing component, summarizes evidence with sensitive information removed, and recommends a safe next action.

• Investigate Muse Code startup or authentication failures
• Diagnose a session that cannot be resumed
• Review earlier activity in a selected Muse Code session

Analyze a project's code and configuration to recommend useful Claude Code automations. Get tailored suggestions for event-triggered actions, specialist agents, reusable skills, plugins, and external tool connections, with reasons for each recommendation.

• Set up Claude Code for a new project
• Find useful formatting and testing automations
• Choose external tool connections for a project's stack

Audit GitHub Codespaces startup time and spending, then identify up to three evidence-based improvements to development containers, machine sizes, prebuilds, or idle timeouts, with validation results and expected impact.

• Investigating slow Codespaces startup
• Reviewing Codespaces spending
• Trimming unused development container components

Present results returned by a Codex helper while preserving findings, severity, file references, and uncertainty. This internal guidance also covers reporting edited files, failed runs, and setup requirements, with user confirmation before fixing review findings.

• Present review findings in order of severity
• Keep observed evidence separate from inferences
• Report files changed by Codex

Explore code structure and history using an index of code relationships and meaning-based search. Trace calls, assess change impact, find likely bug locations, generate architecture reports, and review pull requests for risk and conflicts.

• Tracing function calls and change impact
• Investigating code locations related to a GitHub issue
• Generating architecture reports and class diagrams

Improve research through repeated Gemini reviews, code changes, experiments, and analysis. The workflow records full feedback and actions, then stops when both the score and readiness criteria are met or the round limit is reached.

• Improving research through repeated external reviews
• Implementing and checking fixes for research weaknesses
• Keeping a complete record of reviews and experiments

Review development plans with external AI tools, then revise and review them again while actionable concerns remain. Choose reviewers and a cycle limit to work toward a plan with resolved review findings.

• Review a development plan before implementation
• Revise plans using feedback from multiple AI reviewers
• Use a local model server to review plans

Delegate code review, development, and research from OpenCode to DeepSeek Harness. The skill checks service readiness, tracks each task, and returns reports or proposed code changes for the main agent to review.

• Get a second opinion on code or architecture
• Delegate code changes to an external agent
• Assign research tasks and track progress

Locate conversation logs for Claude Code or Codex CLI and replace the latest assistant response with a fixed agreement message. A dry-run option previews the target without writing changes to the log.

• Replacing the latest assistant response in a conversation log
• Previewing the target response without changing files
• Locating session logs for Claude Code or Codex CLI

Review uncommitted changes, commits, branch differences, or pull requests in context. Identify bugs and concrete security weaknesses, explain when each issue occurs and how serious it is, and provide actionable feedback grounded in the surrounding code.

• Reviewing uncommitted changes before a commit
• Checking a specific commit or branch difference
• Reviewing a pull request before merging

Review code changes and pull requests for correctness, security, performance, and test quality. The skill helps prioritize issues, write specific and constructive feedback, and create shared review checklists and standards for a development team.

• Reviewing code changes and pull requests
• Writing review comments with clear priorities and fixes
• Creating shared review checklists for a team