vimalinx/bio-agent / .claude/skills/bed-to-igv
bed-to-igv
VerifiedUse when you need to generate an IGV batch script for taking snapshots at loci defined in BED, GFF, or VCF files, especially for repeatable visual review of many regions.
bed-to-igv
Quick Start
- Command:
bedToIgv -i loci.bed -path snapshots/ [options] > review.igv.batch - Local executable:
/home/vimalinx/miniforge3/envs/bio/bin/bedToIgv - Full reference: See
references/help.md
When To Use This Tool
- Generate repeatable IGV snapshot scripts for a BED / GFF / VCF locus list.
- Automate review of peaks, variants, breakpoints, or candidate loci across many regions.
- Preload an IGV session with
-sessbefore snapshotting. - Standardize snapshot naming, flanking context, read sorting, and collapse settings across a review batch.
Common Patterns
# 1) Basic IGV batch script for a BED file
bedToIgv \
-i loci.bed \
-path snapshots \
> loci.igv.batch
# 2) Load a saved IGV session and use the BED name field for filenames
bedToIgv \
-i peaks.bed \
-path snapshots \
-sess tumor-review.xml \
-name \
-slop 250 \
> peaks.igv.batch
# 3) Sort alignments and collapse reads before each image
bedToIgv \
-i variants.vcf \
-path snapshots \
-sort position \
-clps \
-img svg \
> variants.igv.batch
Recommended Workflow
- Prepare the BED / GFF / VCF interval list and decide whether an existing IGV session should be loaded with
-sess. - Decide where IGV should save the snapshots via
-path, whether filenames should come from column 4 via-name, and whether flanking context is needed with-slop. - Run
bedToIgvand redirect stdout into a batch-script file. - Open IGV, load the appropriate genome and tracks (or let
-sessdo it), then execute the batch script from within IGV.
Guardrails
-pathsets the snapshot directory used inside IGV; it does not choose where the batch script itself is written.- The command writes the IGV batch script to stdout, so redirect it to a file explicitly.
-nameassumes column 4 is populated with safe, unique names; otherwise the defaultchr:start-end.extnaming is safer.- The generated script must be run from within IGV, not from the shell.
- Without
-sess, you must load the correct genome and tracks in IGV before running the script.
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: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | 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: 319k | 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: 319k | Updated | Claude CodeCodex | Verified | Install |