Results for “code review”

Pre-commit code quality review for Unity C# code. Checks against Rules, CODING_STANDARDS.md, NAMING_CONVENTIONS.md, and GDD Gherkin test coverage. Use when code has been written and tests are passing but before committing. Runs automatically at Step 8.5 of /uw-cmd-implement-feature. Triggers on "review this code", "check my implementation", "pre-commit review", "code review", "check before commit", "is this ready to commit", "review my changes", or any request to validate code quality before committing.

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

Multi-pass structural code review with adversarial analysis, scope-aware dispatch, adversarial persona passes, and forced-finding protocol. Supports input modes: branch diff (default), PR number (#123), commit hash, pending changes (--pending). Use when asked to "review this PR", "code review", "pre-landing review", "check my diff", or "review #123". Proactively suggest when the user is about to merge or land code changes. NOT for behavioral verification against a running build (see mk:evaluate); NOT for post-implementation simplification (see mk:simplify).

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

本スキルを実行している AI(メインレビュアー)と Codex CLI による並列コードレビュー。親で差分・コンテキストを 1 回だけ収集し、メインレビュー（全観点を一括レビュー）と Codex（`/codex-review` 経由）を並列実行、結果を統合した review.md / review.html を生成する。

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

クロスレビュー。有識者エージェント3つの並行レビュー + Codex レビュー + Codex 敵対的レビュー（red team）で変更を多視点レビューし、結果を統合報告する（コードは変更しない）。「クロスレビューして」「cross-reviewして」「複数視点でレビューして」で発動。Codex 単体で足りる軽いレビューは codex-review、レビュー結果の修正・実装まで任せる場合は forge を使う。

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

Evaluate code review feedback against the actual code, supported environments, and existing behavior. Clarify uncertain requests, respond with technical evidence, and implement valid changes one at a time with tests for each fix.

• Clarifying ambiguous code review comments
• Checking whether suggested changes preserve compatibility
• Assessing whether a requested feature is actually used

Implement work described in a specification or tickets, checking types and running tests along the way. Review the completed changes with the code-review skill, then commit the implementation to the current branch.

• Implementing a feature from a specification
• Implementing a referenced issue tracker ticket
• Checking changes with types and tests

Review code changes from a chosen Git reference against two separate criteria: documented coding standards and the original requirements. Independent reviewers check each criterion, then present findings separately so convention problems and requirement gaps remain visible.

• Reviewing changes on a branch or pull request
• Checking changes since a chosen commit or tag
• Checking compliance with documented coding standards

Audit Claude Code configuration with AgentShield to find exposed secrets, excessive permissions, unsafe hooks, and prompt injection risks, where malicious instructions influence an agent. Generate reports, apply supported automatic fixes, or create a security-focused starter configuration.

• Checking configuration when starting a Claude Code project
• Auditing permission and MCP configuration changes
• Reviewing existing configuration in a newly joined repository

Coordinate parallel AI agent sessions with dmux, a tool that manages terminal panes. Split development, research, testing, or review into separate tasks, isolate overlapping file changes, and review results before merging them.

• Running research and implementation in parallel
• Splitting database, API, and UI work across agents
• Coordinating test monitoring and fixes

Review Claude Code settings for duplicate skills, outdated memory files, unused permissions, and other clutter. The workflow presents evidence for each candidate, requests individual approval, and records reversible cleanup actions.

• Reviewing overlaps after installing many skills
• Checking outdated memory files and unused hooks
• Organizing duplicate permission entries

Review code changes and produce concise comments ready to paste into a pull request. Each finding includes its location, the problem, and a concrete fix, with fuller explanations for security issues, architectural disagreements, or authors who need context.

• Reviewing a pull request
• Shortening lengthy review comments
• Pairing findings with concrete fixes

Find agent skills for installed coding tools such as Claude Code and Codex. Use OmniRoute to detect available tools, review relevant GitHub matches, and guide installation into each tool’s skill directory.

• Find skills for installed coding tools
• Review GitHub matches by relevance
• Install a skill into multiple tools

Inspect a codebase and create concise project instructions for Claude Code. Review existing guidance, separate team rules from personal preferences, and propose reusable skills or hooks that run commands automatically.

• Set up project instructions for Claude Code
• Review and improve an existing CLAUDE.md
• Separate personal preferences from team rules

Analyze a codebase and create a CLAUDE.md guide for future Claude Code sessions. Capture build and test commands, explain the overall architecture, and incorporate relevant information from existing documentation and development rules.

• Create a CLAUDE.md guide for a codebase
• Document build, lint, and test commands
• Explain the overall code architecture

Review a specified code change without editing files. Checks the full diff, surrounding code, tests, and callers to identify actionable defects introduced by the change, then reports findings by severity with file and line references.

• Review uncommitted changes for concrete defects
• Check changes that would merge into a base branch
• Review a specific commit and identify test gaps

Review concrete code for exploitable security defects, including missing access checks, unsafe input handling, and exposed secrets. Report verified issues with file locations, reachable attack paths, severity, and suggested fixes.

• Review a code change for exploitable vulnerabilities
• Check authentication and access controls
• Trace unsafe input handling and secret exposure

Create a local Codewhale plugin bundle with a versioned manifest and Skills named with the plugin prefix. Validate its structure and present review results so a person can decide whether to trust and enable it.

• Create a local Codewhale plugin scaffold
• Package Skills under a plugin-specific prefix
• Add required MCP server settings

Turn an understood task into an ordered implementation plan in Codewhale. Clarify the goal and constraints, identify which steps depend on others, and record verification methods, risks, and open questions before broader implementation begins.

• Planning implementation for a clearly defined task
• Ordering steps that depend on one another
• Adding verification to risky steps

Work through GitHub pull request feedback by classifying findings, fixing code, running repository checks, and posting replies. With suitable permissions, the skill repeats Copilot reviews until the latest code is reviewed and every thread has an agent response.

• Address outstanding Copilot review comments
• Run repeated reviews on a completed pull request
• Explain declined suggestions and hand off design decisions

Coordinates specialist agents in Claude Code to work from product requirements through design, implementation, testing, deployment, and operations. Includes task queues, saved progress, parallel reviews, and recovery workflows for managing extended development work.

• Turning product requirements into development tasks
• Coordinating implementation, testing, and reviews
• Resuming extended work from saved progress

Review code changes for security, performance, correctness, and maintainability. Get findings tied to files and lines, severity ratings, practical suggestions with code examples, and a recommendation to approve, request changes, or discuss further.

• Reviewing a pull request before merging
• Checking authentication and injection risks
• Finding excessive database queries and resource leaks

Review completed code changes against the original requirements, choosing review depth by behavioral risk. Coordinate independent reviewers, resolve actionable findings, and verify that the delivered changes match the content actually reviewed.

• Review completed changes before final verification
• Choose review depth based on behavioral risk
• Re-review fixes after actionable findings

Guide substantial qwen-code feature development from investigation and design through implementation, testing, and review. Produce design documents and end-to-end test plans, compare behavior before and after changes, and address verified review findings.

• Developing features that span multiple files
• Documenting a design before implementation
• Comparing behavior before and after a change

Review local uncommitted changes, verify findings, and repeat focused repairs until the review converges or a blocker remains. Also supports Qwen Code issue fixes and review responses within workflows run through GitHub Actions.

• Review and repair local uncommitted changes
• Develop a focused fix for a selected issue
• Verify and address pull request feedback