ワンクリックで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.