This guide covers three things: analyzing one file, scanning a repository for the worst offenders, and producing a per-PR metric report from CI.Documentation Index
Fetch the complete documentation index at: https://mehen.ophi.dev/llms.txt
Use this file to discover all available pages before exploring further.
Install mehen
See the full installation guide. The shortest path:
Analyze a single file
mehen metrics is the one-file command. It auto-detects the language and emits a report in
JSON (default), Markdown, YAML, or TOML.Find the worst offenders in a tree
mehen top-offenders walks one or more paths and ranks the files by one or more metrics:+
or - prefixes when you want different ordering.Diff metrics on a PR
mehen diff compares two git revisions. This is the workhorse behind the
GitHub Action:Add the GitHub Action
Drop a few lines into See the GitHub Action guide for thresholds, monorepos, and the sticky
comment template.
.github/workflows/mehen.yml to publish a metric trend on every PR:Where to next
Pick a metric
Read what each metric means, with formulas and references.
Markdown analysis
Documentation Maintainability Index, link debt, filler/lazy risk, prose layer.
GitHub Action
Inputs, outputs, thresholds, and PR comment design.
Concepts
How mehen organizes parsers, analyzers, and the metric pipeline.