원클릭으로 Manus에서 모든 스킬 실행

code-review

스타2

포크0

업데이트2026년 6월 10일 00:37

Reviews proposed changes to hmfast for correctness, JAX compatibility, API layering, test coverage, and hardware-cost surprises. Use when the user asks for a review, a sanity check on a diff, or before merging a feature branch.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

licongxu

licongxu/JXPaint

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Code review

What to check, in order

Physics correctness. Units, sign conventions, mass-definition consistency, integration limits.
JAX safety. No tracer leaks; no Python-level if / for on traced values; static args declared on @jit; emulator initialization not inside jitted scopes (see .claude/rules/jax-and-numerics.md).
API layering. Tracer / profile boundaries respected; no halo-model integrals duplicated outside HaloModel (see .claude/rules/api-layering.md).
Tests. New public behavior has at least a shape and finiteness test; numerical claims have a tolerance-based comparison.
Hardware cost. Estimate peak memory and runtime for the new code path. Flag anything that violates .claude/rules/cluster-usage.md.
Style. Type hints, docstrings, no print-debugging, no drive-by reformatting (see .claude/rules/python-style.md).

Process

Read the diff: git diff main...HEAD.
Read each touched file in full, not just the hunks.
Run pytest for the touched modules; report failures verbatim.
Produce a written review with Blocking, Suggested, and Nit sections. Each item cites file:line. If a section is empty, write "none".

Do not modify code in a review pass. Suggest edits instead.

이 저장소의 다른 Skills

같은 저장소

cosmology-emulators

licongxu/JXPaint

Guides changes to hmfast Cosmology, emulator loading, and cosmological parameter sets. Use when editing cosmology.py, emulator_load.py, download.py, or adding new emulator_set keys.

2026-06-102

debug-hpc-job

licongxu/JXPaint

Diagnoses a failed or stuck SLURM/HPC job for hmfast (OOM, timeout, NaNs, CUDA errors, missing outputs). Use when the user asks "why did my job fail" or shows a SLURM log.

2026-06-102

halo-model-workflow

licongxu/JXPaint

Guides edits to hmfast's differentiable JAX halo model (HaloModel, mass function, bias, concentration, profiles). Use when changing src/hmfast/halos/, power-spectrum methods, or halo-model consistency flags.

2026-06-102

run-experiment

licongxu/JXPaint

Plans and launches an hmfast experiment (training, inference, or scan) on the cluster with safe resource limits. Use when the user wants to run something that costs nontrivial compute, especially on GPU.

2026-06-102

tracers-and-profiles

licongxu/JXPaint

Guides adding or modifying hmfast tracers and halo profiles. Use when editing src/hmfast/tracers/ or src/hmfast/halos/profiles/, or integrating new observables with HaloModel.

2026-06-102

write-paper-section

licongxu/JXPaint

Drafts or revises a section of an astrophysics or cosmology manuscript based on hmfast results. Use when the user asks for a draft, an edit pass, or a publishability review of a section, including its figures.

2026-06-102

name	code-review
description	Reviews proposed changes to hmfast for correctness, JAX compatibility, API layering, test coverage, and hardware-cost surprises. Use when the user asks for a review, a sanity check on a diff, or before merging a feature branch.

Code review

What to check, in order

Physics correctness. Units, sign conventions, mass-definition consistency, integration limits.
JAX safety. No tracer leaks; no Python-level if / for on traced values; static args declared on @jit; emulator initialization not inside jitted scopes (see .claude/rules/jax-and-numerics.md).
API layering. Tracer / profile boundaries respected; no halo-model integrals duplicated outside HaloModel (see .claude/rules/api-layering.md).
Tests. New public behavior has at least a shape and finiteness test; numerical claims have a tolerance-based comparison.
Hardware cost. Estimate peak memory and runtime for the new code path. Flag anything that violates .claude/rules/cluster-usage.md.
Style. Type hints, docstrings, no print-debugging, no drive-by reformatting (see .claude/rules/python-style.md).

Process

Read the diff: git diff main...HEAD.
Read each touched file in full, not just the hunks.
Run pytest for the touched modules; report failures verbatim.
Produce a written review with Blocking, Suggested, and Nit sections. Each item cites file:line. If a section is empty, write "none".

Do not modify code in a review pass. Suggest edits instead.