review-julia

Review Julia Code

Run a comprehensive Julia code review on the specified script(s). Do NOT edit any source files -- produce a report only.

Steps

1. Identify target: Use $ARGUMENTS to find the Julia file(s). If all, scan all .jl files in the project.

1. Read standards from .claude/rules/julia-code-conventions.md.

1. Check these categories:

• Module Structure: Proper module organization, exports, includes
• Parallel Computing: @everywhere annotations, pmap usage, worker data distribution
• Optimization: Convergence checks, multiple starting values, grid search patterns
• Type Stability: Concrete types in hot loops, @code_warntype recommendations
• Path Conventions: joinpath() usage, no hardcoded OS-specific separators
• Naming: snake_case functions, CamelCase types, paper notation alignment
• Common Pitfalls: Missing @everywhere, local minima, large closures in pmap

1. Save report to quality_reports/[script_name]_julia_review.md.

1. Present summary: Total issues, severity breakdown, top critical issues.

Important

• NEVER edit source files. Report only.
• Prioritize correctness and performance over style.
• For Julia code generation patterns (MLE, GMM, simulation), see /econometrics-julia.