hpc-code-reviewer

Identify correctness issues in parallel CUDA, OpenMP, and OpenCL code.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/SamyakJhaveri/loam --skill hpc-code-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hpc-code-reviewer
Source: https://github.com/SamyakJhaveri/loam/tree/main/seed/_research/skills/hpc-code-reviewer
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill hpc-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured checklist to identify correctness issues in parallel CUDA, OpenMP, and OpenCL code, including data races, memory-model violations, and synchronization bugs, especially when reviewing translated code, auditing benchmark sources, or documenting failure modes.

Core Features & Use Cases

  • Comprehensive review checklist covering data races, memory model violations, synchronization bugs, numerical precision issues, and API-specific pitfalls across CUDA, OpenMP, and OpenCL.
  • Practical guidance for auditing benchmark sources, reviewing LLM-generated translations, and preparing academic analyses of failure modes.
  • Triggered by explicit review requests or when evaluating parallel kernels to ensure root-cause analysis and reproducible results.

Quick Start

Run the HPC Code Reviewer on your parallel kernels to systematically identify and root-cause correctness issues.

Frequently Asked Questions about hpc-code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review parallel CUDA code for data races and synchronization bugs?

To review parallel CUDA code for data races, apply a structured reviewer checklist that systematically identifies correctness issues like memory model violations, synchronization bugs, numerical precision issues, and API-specific pitfalls to ensure root-cause analysis.

What are common failure modes in OpenMP and OpenCL translations?

Common failure modes in OpenMP and OpenCL translations include data races, memory model violations, synchronization bugs, and numerical precision issues. A structured review checklist identifies these API-specific pitfalls to document failure modes and ensure reproducible results.

How do I audit benchmark sources for correctness in high performance computing?

To audit benchmark sources for correctness in high performance computing, evaluate parallel kernels using a structured checklist covering data races, memory model violations, and synchronization bugs. This ensures root-cause analysis and reproducible results across CUDA, OpenMP, and OpenCL code.

Can I use a checklist to find numerical precision issues in parallel kernels?

Yes, you can use a structured reviewer checklist to find numerical precision issues in parallel kernels. The checklist systematically covers data races, memory model violations, synchronization bugs, and API-specific pitfalls across CUDA, OpenMP, and OpenCL code.

What is the best way to identify memory model violations in LLM-generated parallel code?

The best way to identify memory model violations in LLM-generated parallel code is to apply a structured reviewer checklist triggered when evaluating parallel kernels. This systematically detects data races, synchronization bugs, and numerical precision issues to ensure reproducible results.