I Built a Free In-Browser Tool That Tells You If Your MT5 Data Is Clean

RedSamerai — Sat, 17 Oct 2026 07:12:08 +0000

Body
You run a backtest, the curve looks good, and then the uncomfortable question lands: is your data actually clean?
Most MT5 CSV exports are dirty — quietly. The terminal hands you a file that looks complete. It is not.

The five failure modes
Gaps. Connection drops, broker outages, re-export windows that stop mid-hour — missing bars that nobody notices until results drift between platforms.
Duplicates. Re-export the same range twice, merge two files, and the same bar appears twice. Inflated volume counts, broken "first bar of the day" conditions.
Zero-volume / zero-price bars. Exchange halts and feed glitches produce bars with no trades. Indicators computed on them are wrong, and the wrongness does not show up on visual inspection.
Timezone ambiguity. MT5 stores bars in broker-local session time. The same CSV read as UTC moves your strategy to a completely different time of day.
Expected vs actual. A known date range + timeframe should contain a known number of bars. If your file has 9,282 bars where 12,276 are expected, something vanished — and you would not know without doing the arithmetic.
What a clean-data check looks like
A useful report answers five numbers per file, in under a minute:
expected bars vs actual bars
missing bars, and how they cluster (one long gap = broker outage; many short = feed drops)
duplicate bars (exact count, not "there might be some")
zero-volume ratio
timezone/session note — the report states its assumption instead of hiding it
Example: 12,276 expected bars, 9,282 present → 2,994 missing, clustered in 2 gaps (2,970 + 16), gap-free ratio 75.6%. That is a file you should not backtest without first understanding why two days vanished.
Healthy baseline: gap-free ≥ 99%, zero duplicates, zero-volume < 1%. If your file fails that, the results above it are an estimate, not a measurement.
Try it — free, no signup
I built a small tool that runs this check in your browser: https://mt5-cleaner.streamlit.app
Drag a CSV in → it detects broker format, timeframe, and range → you get the quality report plus a cleaned CSV. Files never leave your browser and are gone when you close the tab. No account, no API key, free up to 200 MB.
The workflow I use before any backtest:
Export history from MT5 (CSV)
Run it through the checker — read the 5 numbers
If gap-free < 99%, re-export with a wider range or a different session before touching the strategy code
Sixty seconds of checking saves hours of debugging a strategy that was never wrong — the data was.
Source: https://github.com/RedSamerai/quantclean
Questions or weird report shapes — post them in the comments, the clustering heuristics are the fun part.

Stop Copy-Pasting Conventional Commits Rules: Auto-Fix Your Commits in CI

RedSamerai — Tue, 13 Oct 2026 11:57:30 +0000

Why this exists

I keep hitting the same wall: my Conventional Commits check fails in CI, I push a fix commit, and that fix commit is itself in the wrong format. Then the PR title is 200 chars, the body is missing the Testing section, and in a monorepo my frontend package allows chore: but the backend doesn't — so I've been copy-pasting commitlint config into every repo.

Most linters stop at "tell you it's wrong." I wanted one that actually fixes it.

What I built

pr-conventional — a GitHub Action that enforces AND auto-fixes Conventional Commits, PR titles, and PR descriptions. It checks every new commit in the push (before..after, up to 20), the PR title, and the PR body.

What "auto-fix" means here

It's not "tell you it's wrong". On every push/PR it:

Amends commit messages — fixes the type, adds a missing scope
Appends missing PR-body sections (What / Why / Testing)
Truncates over-long PR titles to your max
Re-validates — only exits 0 when it's genuinely clean

This is the core of the tool, and it's in the FREE tier — no key needed.

Monorepo routing (the part that saves hours)

monorepo:
  packages:
    - path: "packages/frontend"
      rules:
        types: [feat, fix, docs, style, chore, test]
        scopeRegex: '^frontend[a-z0-9-]*$'
    - path: "packages/backend"
      rules:
        types: [feat, fix, refactor, test]

A commit touching packages/frontend/a.ts is validated against the frontend rules. Touching both? It's checked against each rule set (strictest semantics, no intersection). Root-level / merge / shallow-clone files fall back to the root config. No copy-pasting five configs.

FREE vs PRO

Feature	FREE (no key)	PRO ($29 one-time)
Commit / PR validation + auto-fix + SARIF	✅	✅
Whole-push check (before..after, not just HEAD)	✅	✅
Monorepo per-package routing	—	✅
Extends / remote rule packs	—	✅

The FREE tier (MIT, no key) already gives you full validation, auto-fix, and SARIF using your repo's root config. PRO adds two things that scale to teams: per-package rule routing and remote rule-pack distribution.

SARIF out of the box

Every run writes pr-conventional.sarif. Pipe it into upload-sarif and findings land in the GitHub Security tab. No extra setup.

Install (30 seconds)

Drop a config into your repo, then call the action from any workflow:

# .github/workflows/pr-check.yml
jobs:
  pr-check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
![Uploading image](...)
      - uses: RedSamerai/pr-conventional@v0.3.2

Grab a starting point from the examples folder: strict.yml (zero-tolerance), relaxed.yml (personal repos, commit-only), monorepo.yml (per-package routing), chinese-team.yml (CN subjects, CN body sections).

Get the Pro license

PRO is a one-time $29 purchase, lifetime key — no subscription, no renewal. It unlocks monorepo routing and extends/remote rule packs. Get the Pro license → (delivered instantly).

Full docs · Marketplace listing

DEV Community: RedSamerai