Run any Skill in Manus with one click

cosim-gpu-codex-review

Stars1

Forks1

UpdatedJuly 7, 2026 at 08:51

Use when delegating independent code review, design review, or focused bug investigation to an AI reviewer. Provides delegation templates and records reviewer evidence; higher-level review flow remains in cosim-gpu-review or cosim-gpu-rlcr-loop.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

gevico

gevico/cosim-gpu-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

name	cosim-gpu-codex-review
description	Use when delegating independent code review, design review, or focused bug investigation to an AI reviewer. Provides delegation templates and records reviewer evidence; higher-level review flow remains in cosim-gpu-review or cosim-gpu-rlcr-loop.

Codex Review

Use an independent AI reviewer for bounded technical review, investigation, or design critique. This skill owns delegation mechanics only. Review policy shared with cosim-gpu-review and cosim-gpu-rlcr-loop lives in ../cosim-gpu-review/references/review/independent-review-contract.md; read it before adversarial review delegation.

Scope

Use this skill for:

adversarial code review from a written brief
single-file or subsystem investigation with explicit questions
design critique of a proposed local change
second opinion when the main investigation is stuck

Do not delegate user interaction, task scoping, build commands, test commands, or final verification. The main agent owns integration and evidence acceptance.

Assignment Template

Each assignment must be self-contained:

# Target
Exact files, symbols, base reference, current HEAD, and non-goals.

# Change Or Review Question
For review: dimensions to inspect and exact diff commands.
For investigation: symptom, search scope, and questions.
For design: current code, constraints, and rejected directions if artifact-backed.

# Acceptance
Expected output format, severity labels, and required evidence.
No project-wide build, test, or lint commands.

Implementation-oriented assignments must require current HEAD as the edit base, diff-scoped formatting only, and no whole-file formatter churn unless the task is explicitly formatting-only.

Adversarial Review Prompt

Prepare the review brief through cosim-gpu-review or cosim-gpu-rlcr-loop. The sub-agent prompt points to that brief and may include exact scoped diff commands. It must not include the implementer's theory, desired result, or dialogue summary.

For cosim-specific prompts, use references/cosim-gpu-review-prompts.md when the touched subsystem matches interrupt handling, PM4, cache or TLB behavior, HSA completion signals, or similar GPU model paths.

Evidence Recording

Save every consultation under the active task workspace:

artifacts/<task-slug>/reviews/codex-<round>-<file>.md
artifacts/<task-slug>/reviews/codex-<round>-summary.md

Record prompt, file scope, response, classification, and disposition. If the reviewer times out or errors, retry once with a narrower scope and record the failure if it still fails.

Provider Notes

Default to Codex for local code review and Gemini for research that needs current external documentation. If the provider is unavailable and setup cost exceeds review value, fall back to manual review and record that choice.

Proxy and sandbox issues are operational details, not review findings. When a sub-agent creates stray files, verify with repository status and remove only files proven to be sub-agent artifacts.

More from this repository

same repository

cosim-gpu-debug

gevico/cosim-gpu-skills

Use as the main entry for cosim debugging: gem5 crashes, assertions, hangs, timeouts, address translation faults, non-PASS test results, guest-side waits, and QEMU exits that may be secondary to gem5. Collect logs, preserve live state when needed, route to gem5 model references, and decide the first failing component.

2026-07-141

cosim-gpu-build

gevico/cosim-gpu-skills

Use when building gem5 or QEMU, checking build provenance, or preserving gem5 incremental builds across worktrees. Delegates to scripts/cosim_build.sh; never hand-roll Docker, scons, or QEMU make commands.

2026-07-071

cosim-gpu-disk-image-edit

gevico/cosim-gpu-skills

Use when the guest disk image needs modification without a full rebuild. Mount with guestmount, add files, systemd services, kernel module config.

2026-07-071

cosim-gpu-flow-plan

gevico/cosim-gpu-skills

Use as the first step for non-trivial cosim testing, debugging, review, or iterative implementation tasks. Do not use for ordinary repository maintenance such as commit splitting, submodule pointer updates, author config, or documentation-only cleanup.

2026-07-071

cosim-gpu-guest

gevico/cosim-gpu-skills

Use when you need to send commands to a running cosim guest. Console pipe interaction, 9p share mount, GPU status check, manual driver load.

2026-07-071

cosim-gpu-info-gathering

gevico/cosim-gpu-skills

Use when collecting, summarizing, auditing, or comparing cosim evidence from artifact directories, large logs, matrices, verdict files, build provenance, or prior conversation records; also use when reducing raw log reads or checking whether existing artifacts lose information. Enforces full raw evidence preservation, bounded reads, source attribution, compact tables, raw-read plans, coverage self-reporting, and unknown-event preservation before analysis.

2026-07-071

name	cosim-gpu-codex-review
description	Use when delegating independent code review, design review, or focused bug investigation to an AI reviewer. Provides delegation templates and records reviewer evidence; higher-level review flow remains in cosim-gpu-review or cosim-gpu-rlcr-loop.

Codex Review

Scope

Use this skill for:

adversarial code review from a written brief
single-file or subsystem investigation with explicit questions
design critique of a proposed local change
second opinion when the main investigation is stuck

Do not delegate user interaction, task scoping, build commands, test commands, or final verification. The main agent owns integration and evidence acceptance.

Assignment Template

Each assignment must be self-contained:

# Target
Exact files, symbols, base reference, current HEAD, and non-goals.

# Change Or Review Question
For review: dimensions to inspect and exact diff commands.
For investigation: symptom, search scope, and questions.
For design: current code, constraints, and rejected directions if artifact-backed.

# Acceptance
Expected output format, severity labels, and required evidence.
No project-wide build, test, or lint commands.

Implementation-oriented assignments must require current HEAD as the edit base, diff-scoped formatting only, and no whole-file formatter churn unless the task is explicitly formatting-only.

Adversarial Review Prompt

Evidence Recording

Save every consultation under the active task workspace:

artifacts/<task-slug>/reviews/codex-<round>-<file>.md
artifacts/<task-slug>/reviews/codex-<round>-summary.md

Record prompt, file scope, response, classification, and disposition. If the reviewer times out or errors, retry once with a narrower scope and record the failure if it still fails.

Provider Notes

Proxy and sandbox issues are operational details, not review findings. When a sub-agent creates stray files, verify with repository status and remove only files proven to be sub-agent artifacts.