Awesome-Agent-Skills-for-Empirical-Research review-julia

Run the Julia code review protocol on Julia scripts. Checks code quality, type stability, parallel computing patterns, and scientific computing standards. Produces a report without editing files.

install

source · Clone the upstream repo

git clone https://github.com/brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/14-luischanci-claude-code-research-starter/dot-claude/skills/review-julia" ~/.claude/skills/brycewang-stanford-awesome-agent-skills-for-empirical-research-review-julia && rm -rf "$T"

manifest: skills/14-luischanci-claude-code-research-starter/dot-claude/skills/review-julia/SKILL.md

source content

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
```
$ARGUMENTS
```
to find the Julia file(s). If
```
all
```
, scan all
```
.jl
```
files in the project.
Read standards from
```
.claude/rules/julia-code-conventions.md
```
.
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
```

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
```
.