Picard's MarkDuplicates or just check the duplication stats from STAR. High duplication (>60%) means you probably sequenced too little input material.
Your "20 million reads" might actually be 5 million unique reads. That changes everything for statistical power.
8/9 Check 7: Count distribution and filtering.
After quantification, look at the distribution of counts per gene. Filter low-count genes (I typically require >10 counts in at least n samples where n = your smallest group size).
Also check for genes driving >5% of total counts. One mitochondrial gene eating half your library is more common than you think.
9/9 I run these 7 checks on every single dataset. No exceptions.
It takes about 30 minutes for a typical experiment. I've written Snakemake pipelines that automate most of it.
The alternative is spending two weeks on a differential expression analysis, presenting results, and having someone ask "did you check for batch effects?" while you stare at the floor.
Anthropic just published "the single most important workflow for using Claude Code." It is four steps: Explore, Plan, Code, Commit.
Every bioinformatician I know who is good at their job has been doing this for years. Just without the AI part. Here is why it maps so cleanly.
Explore.
For Claude Code: read the relevant files before touching anything. Understand what exists. Map the dependencies.
For bioinformatics: look at the data before you analyze it. Plot the distributions. Check the metadata. Count the NAs. Ask the wet-lab person what they actually did. Read the existing pipeline.
It is a classifier that decides which permission prompts you actually need to see. Safe reads and routine commands run without interrupting you. Anything that looks risky still gets blocked and surfaced for approval.
If you have ever felt like Claude Code is asking you to approve `ls` for the hundredth time today, this is for you.
Before auto mode there were two bad choices.
Approve everything one prompt at a time and spend half your day clicking yes. Or run with `--dangerously-skip-permissions` and pray the model never decides to be creative about which directory to delete from.
Claude Code's /ultraplan is one of the AI feature in a while that actually changed my workflow instead of just speeding it up.
btw, I always use /plan for a new task. /ultraplan is different.
You ask for a plan from your CLI. It gets drafted in the cloud.
You keep coding. A few minutes later you tab over to your browser and the plan is sitting there, and you can highlight any sentence and leave a note on it.
That's it. That's the whole pitch. And it's better than it sounds.
I had not realized how bad the chat interface is for planning until I stopped using it.
Claude Code shipped /ultrareview and almost nobody is talking about what's actually new about it.
It's not "AI reviews your code." We had that.
It's a fleet of reviewer agents that run in the cloud, find bugs in parallel, and then independently reproduce and verify every finding before showing it to you.
Verification is the part everyone is missing.
Single-agent code review has a known weakness: the model decides what to focus on, and you get whatever it noticed.
If it spent its attention budget on naming, you don't hear about the security bug.