review

Review analytical code and scientific changes using six specialized checklists and synthesized findings.

68|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/arjunrajlaboratory/mycelium --skill review-arjunrajlaboratory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/arjunrajlaboratory/mycelium/tree/main/skills/review
Command: npx skills add https://github.com/arjunrajlaboratory/mycelium --skill review-arjunrajlaboratory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Analytical code often runs cleanly while producing silently wrong results — wrong statistical tests, data leakage, or fabricated outputs — and these errors slip past generic code review. This Skill audits PRs, commits, diffs, and working trees for the failure modes that matter in scientific data work. ## Core Features & Use Cases - Six specialized review passes: statistics/causal inference, data pipeline leakage, bioinformatics, LLM failure modes, documentation fidelity, and code quality, each with its own checklist. - Prioritized synthesis: findings are deduplicated, recalibrated to Major/Minor severity, grouped by category, and written to a dated report under .living/outputs/reviews/. - Grill mode and tripwires: conversationally interrogate consequential analytical decisions one question at a time, or design perturbation tests that verify the pipeline fails at named scientific boundaries. - Use Case: Before merging a PR that adds a differential expression analysis, run the review to catch pseudoreplication, uncorrected multiple comparisons, and report numbers that no longer match the source CSV. ## Quick Start Ask the assistant to review the current working tree or a specific PR for statistical, leakage, and code-quality issues using the mycelium review skill.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request for statistical and data pipeline errors?

Invoke the review with a PR number or URL; it fetches the diff with gh, runs six specialized checklists covering statistics, leakage, bioinformatics, LLM failure modes, documentation, and code quality, then writes a prioritized report to .living/outputs/reviews/.

What kinds of issues does an analytical code review catch?

It catches silent scientific errors: wrong test selection, multiple-comparison problems, train/test leakage, time-series look-ahead, pseudoreplication, hallucinated APIs, try/except antipatterns, and documentation that has drifted from actual behavior.

Can I review a git commit range or working tree instead of a PR?

Yes. The review accepts commit SHAs, ranges like sha1..sha2, branch-versus-main diffs, the dirty working tree, pasted diffs, or an entire analysis directory treated as added files.

What is grill mode in an analysis review?

Grill mode walks you through every consequential analytical decision one conversational question at a time, then summarizes which choices had clear justifications and which deserve follow-up. Trigger it by including 'grill' in the invocation.

When should I not use this review skill?

Do not use it for writing new analyses, generating reports, project initialization, stylistic linting, or pure software review with no analytical component. It targets scientific correctness, not general refactoring.