dev-physics-review

Review physics lesson code for correctness, safety, and documentation gaps.

36|6|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Nebulavenus/forge-gpu --skill dev-physics-review-nebulavenus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-physics-review
Source: https://github.com/Nebulavenus/forge-gpu/tree/main/.claude/skills/dev-physics-review
Command: npx skills add https://github.com/Nebulavenus/forge-gpu --skill dev-physics-review-nebulavenus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure physics lesson implementations are correct, well-documented, and maintainable by performing structured reviews across code, tests, and docs.

Core Features & Use Cases

  • Phase 1 — Code correctness sweep: spawn agents for memory safety, parameter validation, bug detection, undefined behavior, resource cleanup.
  • Phase 2 — Verification checks: checks 1-9 across tests and setup.
  • Phase 3 — Documentation and content verification: doc checks.

Quick Start

Run the reviewer against the physics lesson to identify issues and guide fixes.

Frequently Asked Questions about dev-physics-review

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

FAQPage Schema
How do I perform a comprehensive physics code review for correctness and safety?

A physics code review identifies correctness, safety, and documentation gaps by applying deterministic steps and static analysis across the codebase, including header files, main implementation, and tests.

What is static analysis for physics code implementation?

Static analysis for physics code uses agent-based reviews to detect memory safety issues, parameter validation errors, and undefined behavior across the codebase without executing the program.

How do I check physics test coverage and verification setup?

You check physics test verification by applying structured checks across test suites and setup configurations to ensure deterministic steps and safety parameters are correctly validated before the final pass.

Can I use automated code review for memory safety and resource cleanup in C physics engines?

Automated code review can spawn dedicated agents to sweep C physics code for memory safety issues, resource cleanup gaps, and undefined behavior across implementation and test files.

What is the best way to verify documentation completeness in a physics codebase?

The best way to verify physics documentation completeness is to run a dedicated review phase that checks content accuracy and structural documentation gaps across the entire physics codebase.

Why does my physics code need a structured review before the final pass?

Your physics code needs a structured review to enforce deterministic steps and static analysis, ensuring correctness, safety, and documentation gaps are identified and guided for fixes before finalizing.