Add technical-debt command for code complexity analysis

Implement comprehensive technical debt analysis with multiple metrics:
- Large commits detection (>20 files changed)
- File hotspots analysis (frequently modified files with risk levels)
- Long-lived branches identification (>30 days old)
- Code churn patterns (high add/delete ratios)
- Binary files detection in repository

Features styled output with emoji indicators, color-coded risk levels,
and comprehensive test coverage including 11 unit tests and 9 integration
tests. Updated documentation and cleaned up CI configuration.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: simeg

.github/workflows/ci.yaml

@@ -61,5 +61,4 @@ jobs:
         with:
           token: ${{ secrets.CODECOV_TOKEN }}
           slug: simeg/git-x
-          files: ./cobertura.xml
           fail_ci_if_error: false

Makefile

@@ -23,10 +23,6 @@ run: build
 test:
 	$(CARGO) test -- --test-threads=1
 
-## Run tests serially (useful for debugging test interference)
-test-serial:
-	$(CARGO) test -- --test-threads=1
-
 ## Run test coverage analysis using tarpaulin
 coverage:
 	$(CARGO) tarpaulin --workspace --timeout 120 --out Stdout
@@ -71,7 +67,6 @@ help:
 	@echo "  make build     Build release binary"
 	@echo "  make run       Run binary with ARGS=\"xinfo\""
 	@echo "  make test      Run tests"
-	@echo "  make test-serial Run tests serially (for debugging)"
 	@echo "  make coverage  Generate test coverage report"
 	@echo "  make fmt       Format code"
 	@echo "  make fmt-check  Check formatting"

README.md

@@ -29,6 +29,7 @@ It wraps common Git actions in muscle-memory-friendly, no-brainer commands — p
     - [`summary`](#summary)
     - [`switch-recent`](#switch-recent)
     - [`sync`](#sync)
+    - [`technical-debt`](#technical-debt)
     - [`undo`](#undo)
     - [`upstream`](#upstream)
     - [`what [branch]`](#what-branch)
@@ -473,6 +474,48 @@ Automatically fetches from remote and integrates upstream changes into your curr
 
 ---
 
+### `technical-debt`
+
+> Analyze code complexity and technical debt metrics
+
+```shell
+git x technical-debt
+```
+
+#### Output:
+
+```shell
+🔍 Technical Debt Analysis
+
+📊 Large Commits (>20 files changed)
+   ✓ No large commits found
+
+🔥 File Hotspots (frequently modified)
+   1. 15 changes | HIGH | src/main.rs
+   2. 8 changes | MED | src/lib.rs
+   3. 6 changes | LOW | README.md
+
+🌿 Long-lived Branches (>30 days)
+   • feature/old-refactor | 3 months ago | Alice Smith
+   • hotfix/legacy-fix | 6 weeks ago | Bob Jones
+
+🔄 Code Churn (high add/delete ratio)
+   1. +245 -189 | HIGH | src/parser.rs
+   2. +156 -98 | MED | src/utils.rs
+
+📦 Binary Files in Repository
+   ! 3 binary files found
+   • assets/logo.png
+   • docs/manual.pdf
+   ...
+
+Analysis complete!
+```
+
+Analyzes repository for technical debt indicators including large commits, file modification hotspots, long-lived branches, code churn patterns, and binary file usage.
+
+---
+
 ### `undo`
 
 > Undo the last commit (without losing changes)

cobertura.xml

@@ -83,6 +83,61 @@ This document explains how each `git-x` subcommand works under the hood. We aim
 
 ---
 
+## `technical-debt`
+
+### What it does:
+- Analyzes repository for technical debt indicators including large commits, file hotspots, long-lived branches, code churn, and binary files.
+
+### Under the hood:
+- **Large Commits Analysis:**
+  ```shell
+  git log --all --pretty=format:%h|%s|%an|%ad --date=short --numstat --since=6 months ago
+  ```
+  - Parses commit history with file change statistics
+  - Identifies commits with >20 file changes
+  - Sorts by number of files changed
+
+- **File Hotspots Analysis:**
+  ```shell
+  git log --all --pretty=format: --name-only --since=6 months ago
+  ```
+  - Counts modification frequency per file
+  - Categorizes risk levels: HIGH (>50), MED (>20), LOW (>5)
+  - Excludes dotfiles and shows top modified files
+
+- **Long-lived Branches Analysis:**
+  ```shell
+  git for-each-ref --format=%(refname:short)|%(committerdate:relative)|%(authorname) refs/heads/
+  ```
+  - Identifies branches older than 30 days
+  - Excludes main/master/develop branches
+  - Estimates days from relative date strings
+
+- **Code Churn Analysis:**
+  ```shell
+  git log --all --pretty=format: --numstat --since=3 months ago
+  ```
+  - Aggregates additions/deletions per file
+  - Calculates churn ratio (total changes / line changes)
+  - Highlights files with high modification-to-content ratios
+
+- **Binary Files Detection:**
+  ```shell
+  git ls-files
+  ```
+  - Scans tracked files for binary extensions
+  - Checks common binary types: images, videos, audio, archives, executables, documents
+  - Reports count and sample file paths
+
+### Key metrics:
+- Large commits indicate lack of atomic changes and potential review complexity
+- File hotspots suggest architectural issues or missing abstractions
+- Long-lived branches indicate potential merge conflicts and outdated code
+- High churn files may need refactoring or better change management
+- Binary files affect repository size and diff readability
+
+---
+
 ## `prune-branches`
 
 ### What it does: