Run any Skill in Manus with one click

Get Started

uni20-code-review

Stars4

Forks0

UpdatedJuly 15, 2026 at 19:36

Review Uni20 changes for correctness, regressions, missing evidence, and architectural consistency.

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

Uni20-dev

Uni20-dev/uni20

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	uni20-code-review
description	Review Uni20 changes for correctness, regressions, missing evidence, and architectural consistency.

Uni20 Code Review

Overview

Use this skill for substantive review of a Uni20 diff, commit, branch, or pull request. The canonical review process and subsystem checklists are in docs/development/code_review.md.

Workflow

Read AGENTS.md and docs/development/code_review.md.
Identify the maintainer-approved contract or canonical design source.
Read changed tests and establish whether their oracle is independent.
Inspect the implementation diff and nearby equivalent paths.
Check the relevant numerical, tensor/mdspan, async/AD, or symmetry checklist.
Report findings first, ordered by severity, with file and line references.
If there are no findings, state that clearly and report residual test or configuration risk.

Constraints

Do not treat policy compliance as proof of correctness.
Do not infer intended behavior solely from current code.
Do not manufacture style findings when the implementation is sound.
Do not edit files unless the user also asks to address the findings.

Reporting Shape

findings ordered as blocker, important, suggestion, or question;
open assumptions that affect correctness;
concise change summary only after the findings;
tests and configurations not exercised.

More from this repository

same repository

uni20-build-and-test

Uni20-dev/uni20

Configure, build, and run tests for the Uni20 repository with project-specific conventions. Keep this skill machine-agnostic and defer local toolchain/path details to .codex/instructions.local.md when available.

2026-07-154

uni20-build-matrix

Uni20-dev/uni20

Run a machine-agnostic Uni20 configure/build/test matrix by detecting available compilers and applying a minimal coverage strategy.

2026-07-154

uni20-cmake-dependency-triage

Uni20-dev/uni20

Diagnose and fix Uni20 dependency detection/configuration failures with minimal, reproducible CMake changes.

2026-07-154

uni20-doxygen-audit

Uni20-dev/uni20

Audit and normalize Uni20 Doxygen comments to AGENTS.md policy with minimal, scoped edits.

2026-06-124

uni20-doc-sync

Uni20-dev/uni20

Keep Uni20 documentation aligned with current code behavior and API surface, with emphasis on async and developer-facing docs.

2026-03-084

name	uni20-code-review
description	Review Uni20 changes for correctness, regressions, missing evidence, and architectural consistency.

Uni20 Code Review

Overview

Use this skill for substantive review of a Uni20 diff, commit, branch, or pull request. The canonical review process and subsystem checklists are in docs/development/code_review.md.

Workflow

Read AGENTS.md and docs/development/code_review.md.
Identify the maintainer-approved contract or canonical design source.
Read changed tests and establish whether their oracle is independent.
Inspect the implementation diff and nearby equivalent paths.
Check the relevant numerical, tensor/mdspan, async/AD, or symmetry checklist.
Report findings first, ordered by severity, with file and line references.
If there are no findings, state that clearly and report residual test or configuration risk.

Constraints

Do not treat policy compliance as proof of correctness.
Do not infer intended behavior solely from current code.
Do not manufacture style findings when the implementation is sound.
Do not edit files unless the user also asks to address the findings.

Reporting Shape

findings ordered as blocker, important, suggestion, or question;
open assumptions that affect correctness;
concise change summary only after the findings;
tests and configurations not exercised.