track-trendslisted

# Track Trends Generate historical analysis of repository health metrics over time to identify improvement or degradation patterns. ## Prerequisites Omen CLI must be installed and available in PATH. ## When to Use - Quarterly engineering health reports - Release retrospectives - Tracking debt paydown initiatives - Justifying refactoring investments with data - Identifying gradual quality degradation ## Workflow ### Step 1: Run Trend Analysis Use the Omen CLI to analyze historical scores: ```bash # Last 3 months, weekly sampling (default) omen score trend --since 3m # Last 6 months for quarterly report omen score trend --since 6m --period monthly # Full year for annual review omen score trend --since 1y --period monthly ``` **Parameters:** - `--since`: How far back to analyze (3m, 6m, 1y, 2y, 30d, 4w, all). Defaults to `all` (full history). - `--period`: Sampling frequency (daily, weekly, monthly) ### Step 2: Interpret Results The output includes: | Field | Meaning | |-------|---------| | Score | Composite health score (0-100) | | Slope | Points gained/lost per period | | R-squared | How consistent the trend is (0-1) | | Correlation | Direction and strength (-1 to 1) | **Trend interpretation:** - Positive slope = improving health - Negative slope = degrading health - High R-squared (>0.7) = consistent trend - Low R-squared (<0.3) = volatile/no clear trend ### Step 3: Analyze Component Trends Each component has its own trend statistics: | Component | What It