complexity-trends

Track drifting code complexity across modules using wily.

Updated Sep 9, 2024
One-click install
npx skills add https://github.com/axel-kaliff/dotfiles --skill complexity-trends
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: complexity-trends
Source: https://github.com/axel-kaliff/dotfiles/tree/main/claude/.claude/skills/complexity-trends
Command: npx skills add https://github.com/axel-kaliff/dotfiles --skill complexity-trends

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Track how complexity changes over time and helps teams identify drift before maintainability suffers.

Core Features & Use Cases

  • Baseline-driven complexity tracking across modules
  • Rank worst offenders and surface trends
  • Diff against baseline to quantify changes

Quick Start

Invoke complexity-trends with an optional target to generate a baseline and reveal drift across modules.

Frequently Asked Questions about complexity-trends

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track code complexity drift over time in a repository?▼

Code complexity drift is tracked by building a baseline from commit history and comparing modules against it. This Skill uses wily to rank worst offenders and produce a focused report showing how maintainability changes across your codebase.

What's the best way to rank files by code complexity trends?▼

To rank files by code complexity, you can apply this Skill to specific modules or files to surface worst offenders. It generates a ranked, drift-focused report by diffing current complexity metrics against a historical baseline.

How do I compare current code complexity against a baseline?▼

Comparing current code complexity against a baseline requires the wily tool and a repository with commit history. The Skill builds a baseline and quantifies changes by diffing modules against it to reveal drifting code quality.

Does tracking code complexity over time require a specific tool?▼

Tracking code complexity over time requires the wily tool and a repository with commit history. Wily builds the baseline needed to analyze drifting complexity across modules and produce focused, ranked reports.

Can I analyze code complexity drift for specific modules or files?▼

You can analyze code complexity drift for specific modules or files by providing an optional target. The Skill applies baseline-driven tracking to the specified target to surface trends and rank the worst offenders.

Why should I monitor code complexity drift in my codebase?▼

Monitoring code complexity drift helps teams identify maintainability issues before they suffer. By tracking how complexity changes over time and diffing against a baseline, you can surface worst offenders and prevent long-term code quality degradation.