docs-analyzer

# Documentation Analyzer Skill

## Purpose

This skill specializes in analyzing codebases to identify documentation gaps and assess the impact of code changes on existing documentation. It provides structured reports to guide documentation updates.

## When to Activate

Use this skill when:
- Starting documentation review for a project
- Analyzing impact of recent code changes
- Auditing documentation completeness
- Preparing for documentation updates
- User requests documentation analysis

## Core Workflow

### Step 1: Catalog Existing Documentation

Scan and catalog all documentation files in the repository:

**Documentation Files to Find**:
- `README.md` (root and subdirectories)
- `docs/` directory contents
- `CONTRIBUTING.md`
- `CHANGELOG.md`
- `*.md` files throughout the codebase
- API documentation (OpenAPI/Swagger specs)
- Architecture diagrams and documentation

**Use Glob and Read tools**:
```bash
# Find all markdown files
Glob: "**/*.md"

# Find documentation directories
Glob: "**/docs/**/*"

# Find API specs
Glob: "**/*.{yaml,yml,json}" (for OpenAPI specs)
```

**Catalog Output**:
- List of all documentation files found
- Brief description of each file's purpose
- Last modified date (from git)
- Current state assessment (complete, outdated, missing sections)

### Step 2: Analyze Git History

Use Bash tool to analyze recent code changes and identify affected components.

**Git Commands to Run**:
```bash
# Get recent commits (last 10-50 depending on activity)
git log --oneline -20

# Get detailed diff for recent changes
git diff HEAD~10..HEAD --stat

# Identify changed files by type
git diff HEAD~10..HEAD --name-only

# Get commit messages for context
git log HEAD~10..HEAD --pretty=format:"%h - %s"
```

**Analyze**:
- Files modified (by extension and directory)
- Commit messages (feature, fix, refactor indicators)
- Areas of codebase affected (frontend, backend, infrastructure, etc.)

### Step 3: Identify Affected Components

Based on file changes, determi