quant-code-review

Identify numerical defects in quantitative-finance Python code causing wrong results.

Updated May 12, 2026
One-click install
npx skills add https://github.com/RorySullivan1/claudeBrain --skill quant-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quant-code-review
Source: https://github.com/RorySullivan1/claudeBrain/tree/main/example-project/.claude/skills/quant-code-review
Command: npx skills add https://github.com/RorySullivan1/claudeBrain --skill quant-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review quantitative-finance Python code to identify defects that produce wrong numbers despite clean tests, focusing on numerical integrity, reproducibility, and proper conventions.

Core Features & Use Cases

  • Detect look-ahead bias, data leakage, precision loss, and unit/convention errors in pricing, risk, and backtesting code.
  • Validate reproducibility with seeded RNGs and pinned data, and provide explanations linking defects to numerical outcomes.
  • Provide a structured review that can be applied to reports, notebooks, and production-style quant pipelines.

Quick Start

Submit a reproducible quant-python snippet to receive a defect-focused, step-by-step review.

Frequently Asked Questions about quant-code-review

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

FAQPage Schema
How do I detect look-ahead bias and data leakage in my backtesting code?

Detecting look-ahead bias and data leakage in backtesting code requires a structured review of numerical integrity, checking for future data exposure, precision loss, and reproducibility issues. Submitting a reproducible Python snippet with pinned data and seeded RNG applies this review to your quant workflows.

Why does my quantitative-finance Python code produce numerically wrong results despite passing tests?

Quantitative-finance Python code often produces numerically wrong results due to hidden defects like look-ahead bias, precision loss, or unit inconsistencies. A targeted code review validates reproducibility with seeded RNGs and links these specific defects to incorrect numerical outcomes.

Can I review time-series pipelines and risk models for numerical correctness without modifying the source code?

You can review time-series pipelines and risk models for numerical correctness by submitting reproducible Python snippets directly for analysis. This evaluates numerical behavior and identifies convention errors in pricing and risk code without modifying the underlying source files.

What do I need to prepare for a quantitative-finance code review?

Preparing for a quantitative-finance code review requires a reproducible Python snippet with pinned data and seeded RNG. This setup verifies numerical behavior and ensures the review can accurately identify look-ahead bias, precision loss, and unit inconsistencies across quant workflows.

Does code review work for validating numerical correctness in pricing models?

Code review works for validating numerical correctness in pricing models by systematically examining the Python logic for convention errors and precision loss. It links identified defects directly to incorrect numerical outcomes in pricing, risk, and backtesting workflows.