brycewang-stanford/Auto-Empirical-Research-Skills / skills/14-luischanci-claude-code-research-starter/dot-claude/skills/review-julia
review-julia
VerifiedRun 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.
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |