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
- •
Identify target: Use
$ARGUMENTSto find the Julia file(s). Ifall, scan all.jlfiles in the project. - •
Read standards from
.claude/rules/julia-code-conventions.md. - •
Check these categories:
- •Module Structure: Proper module organization, exports, includes
- •Parallel Computing:
@everywhereannotations,pmapusage, worker data distribution - •Optimization: Convergence checks, multiple starting values, grid search patterns
- •Type Stability: Concrete types in hot loops,
@code_warntyperecommendations - •Path Conventions:
joinpath()usage, no hardcoded OS-specific separators - •Naming:
snake_casefunctions,CamelCasetypes, paper notation alignment - •Common Pitfalls: Missing
@everywhere, local minima, large closures inpmap
- •
Save report to
quality_reports/[script_name]_julia_review.md. - •
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.