health

name	health
description	Perform comprehensive project health checks with fast (read-only) and full (build/test/dependency) modes, generating detailed Markdown reports with actionable suggestions

Health Check Skill

Overview

This skill performs comprehensive health checks on your project and generates a detailed Markdown report. The health check is report-only — it will never block your workflow or make automatic changes to your codebase. The report highlights issues, warnings, and suggestions to help you maintain project health.

Modes

Mode	Description	Checks	Duration
Fast	Default mode; read-only checks only	1-8 (Commit, Branch, Code-Doc, Doc, Skill, Code Size, Recent Changes, Test Matrix)	< 1 minute
Full	Includes build, test, and coverage checks	All 12 checks	2-10 minutes

Usage:

• Fast mode (default): Just run the skill normally
• Full mode: Specify "full mode" or "run full health check" when invoking

Workflow

1. Determine mode — Default to Fast unless "full mode" is requested
2. Detect project type — Identify package.json, Cargo.toml, go.mod, pyproject.toml, etc.
3. Run checks — Execute each check based on mode
4. Generate report — Create Markdown report with summary and details
5. Show summary — Display key findings and suggestions

Check Items

1. 提交状态 (Commit Status) — FAST

Purpose: Verify clean working directory and recent activity

Check Instructions:

# Check for uncommitted changes
git status --short

# Check for recent commits (within last 7 days)
git log --since="7 days ago" --oneline | head -5

# Check for untracked files (excluding .git/ and node_modules/)
git ls-files --others --exclude-standard | head -10

PASS Criteria:

• No uncommitted changes (empty git status --short)
• At least one commit within the last 7 days
• No untracked files (or only expected files like .env.example)

WARN Criteria:

• Uncommitted changes present
• No commits within the last 7 days (but within 30 days)
• Few untracked files (< 5)

FAIL Criteria:

• No commits within the last 30 days
• Many untracked files (≥ 10)

SKIP Criteria:

• Not a git repository

---

2. 分支同步 (Branch Sync) — FAST

Purpose: Verify branch synchronization with remote and identify stale branches

Check Instructions:

# Check current branch ahead/behind status
git rev-list --left-right --count HEAD...@{u} 2>/dev/null || echo "No upstream"

# List all branches with last commit date
git for-each-ref --format='%(refname:short) %(committerdate:relative)' refs/heads/

# Check for stale branches (no commits in 90+ days)
git for-each-ref --format='%(refname:short) %(committerdate:relative)' refs/heads/ | grep -E "[89][0-9] days ago|[0-9]+ (months|years) ago"

PASS Criteria:

• Current branch is up-to-date with remote (no ahead/behind)
• No stale branches (all branches active within 90 days)

WARN Criteria:

• Current branch ahead or behind remote by 1-5 commits
• 1-2 stale branches present

FAIL Criteria:

• Current branch ahead or behind remote by > 5 commits
• 3+ stale branches present
• No remote configured

SKIP Criteria:

• Not a git repository
• No remote configured

---

3. 代码-文档一致性 (Code-Doc Consistency) — FAST

Purpose: Verify code and documentation stay in sync

Check Instructions:

# Find code files (based on project type)
if [ -f "package.json" ]; then
  find src/ -name "*.ts" -o -name "*.js" -o -name "*.tsx" -o -name "*.jsx" 2>/dev/null | head -20
elif [ -f "Cargo.toml" ]; then
  find src/ -name "*.rs" 2>/dev/null | head -20
elif [ -f "go.mod" ]; then
  find . -name "*.go" -not -path "./vendor/*" 2>/dev/null | head -20
elif [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; then
  find . -name "*.py" -not -path "./venv/*" -not -path "./.venv/*" 2>/dev/null | head -20
fi

# Find documentation files
find . -name "*.md" -not -path "./node_modules/*" -not -path "./target/*" -not -path "./.git/*" 2>/dev/null | head -20

# Check for outdated TODO/FIXME comments
grep -r "TODO\|FIXME" --include="*.ts" --include="*.js" --include="*.rs" --include="*.go" --include="*.py" . 2>/dev/null | head -10

PASS Criteria:

• Documentation files exist and are recently modified (within 30 days)
• No TODO/FIXME comments older than 60 days
• README.md exists and mentions key features

WARN Criteria:

• Documentation files exist but not recently modified (30-90 days)
• 1-5 TODO/FIXME comments present
• README.md missing or outdated

FAIL Criteria:

• No documentation files found
• Many TODO/FIXME comments (≥ 10)
• README.md completely missing

SKIP Criteria:

• No code files detected

---

4. 文档完整性 (Doc Completeness) — FAST

Purpose: Verify required documentation files exist and are complete

Check Instructions:

# Check for required documentation
for doc in README.md CONTRIBUTING.md LICENSE CHANGELOG.md .github/CONTRIBUTING.md docs/CLAUDE.md CLAUDE.md; do
  if [ -f "$doc" ]; then
    echo "✓ $doc exists"
    wc -l "$doc" | awk '{print "  Lines:", $1}'
  else
    echo "✗ $doc missing"
  fi
done

# Check for API docs (if applicable)
if [ -f "package.json" ]; then
  [ -d "docs/api" ] && echo "✓ API docs exist" || echo "✗ API docs missing"
fi

PASS Criteria:

• README.md exists with ≥ 20 lines
• At least one of: CONTRIBUTING.md or .github/CONTRIBUTING.md
• LICENSE file exists

WARN Criteria:

• README.md exists but < 20 lines
• CONTRIBUTING.md missing
• CHANGELOG.md missing

FAIL Criteria:

• README.md missing
• LICENSE file missing

SKIP Criteria:

• N/A (always run)

---

5. 技能完整性 (Skill Integrity) — FAST

Purpose: Validate SKILL.md frontmatter and structure (for SUMM-Powers projects)

Check Instructions:

# Find all SKILL.md files
find skills/ -name "SKILL.md" 2>/dev/null

# Validate frontmatter for each SKILL.md (only within frontmatter delimiters)
for skill in skills/*/SKILL.md; do
  if [ -f "$skill" ]; then
    echo "Checking $skill:"
    # Extract frontmatter only (between first two --- lines)
    frontmatter=$(sed -n '2,/^---$/p' "$skill" | head -20)
    echo "$frontmatter" | grep -q "^name:" && echo "  ✓ name" || echo "  ✗ Missing name"
    echo "$frontmatter" | grep -q "^description:" && echo "  ✓ description" || echo "  ✗ Missing description"
    # Check for required sections
    grep -q "## Overview" "$skill" && echo "  ✓ Overview section" || echo "  ✗ Missing Overview"
  fi
done

PASS Criteria:

• All SKILL.md files have valid frontmatter (name and description)
• All SKILL.md files have Overview section

WARN Criteria:

• Some SKILL.md files missing recommended sections
• Minor frontmatter inconsistencies

FAIL Criteria:

• SKILL.md files missing frontmatter
• SKILL.md files missing name or description

SKIP Criteria:

• No skills/ directory found (not a SUMM-Powers project)

---

6. 代码规模 (Code Size) — FAST

Purpose: Measure total lines of code and breakdown by language

Check Instructions:

# Count total lines of code by file type
# Adapt extensions based on detected project type
if [ -f "package.json" ]; then
  echo "=== TypeScript/JavaScript ==="
  find src/ -name "*.ts" -o -name "*.js" -o -name "*.tsx" -o -name "*.jsx" 2>/dev/null | xargs wc -l 2>/dev/null | tail -1
  echo "=== Styles (CSS/SCSS) ==="
  find src/ -name "*.css" -o -name "*.scss" -o -name "*.less" 2>/dev/null | xargs wc -l 2>/dev/null | tail -1
elif [ -f "Cargo.toml" ]; then
  echo "=== Rust ==="
  find src/ -name "*.rs" 2>/dev/null | xargs wc -l 2>/dev/null | tail -1
elif [ -f "go.mod" ]; then
  echo "=== Go ==="
  find . -name "*.go" -not -path "./vendor/*" 2>/dev/null | xargs wc -l 2>/dev/null | tail -1
elif [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; then
  echo "=== Python ==="
  find . -name "*.py" -not -path "./venv/*" -not -path "./.venv/*" 2>/dev/null | xargs wc -l 2>/dev/null | tail -1
fi

# Generic fallback — count all common source files
echo "=== All source files ==="
find . -type f \( -name "*.ts" -o -name "*.js" -o -name "*.tsx" -o -name "*.jsx" -o -name "*.rs" -o -name "*.go" -o -name "*.py" -o -name "*.java" -o -name "*.rb" \) \
  -not -path "./node_modules/*" -not -path "./vendor/*" -not -path "./.venv/*" -not -path "./venv/*" -not -path "./target/*" -not -path "./.git/*" \
  2>/dev/null | xargs wc -l 2>/dev/null | tail -1

# Count total files
find . -type f \( -name "*.ts" -o -name "*.js" -o -name "*.tsx" -o -name "*.jsx" -o -name "*.rs" -o -name "*.go" -o -name "*.py" -o -name "*.java" -o -name "*.rb" \) \
  -not -path "./node_modules/*" -not -path "./vendor/*" -not -path "./.venv/*" -not -path "./venv/*" -not -path "./target/*" -not -path "./.git/*" \
  2>/dev/null | wc -l

# Count total lines (including config, markdown, etc.)
echo "=== Total lines (all text files) ==="
git ls-files 2>/dev/null | xargs wc -l 2>/dev/null | tail -1

PASS Criteria:

• Source files detected and countable
• Total lines reported successfully

WARN Criteria:

• Very large codebase (> 100,000 LOC) — consider splitting
• No clear language breakdown possible

FAIL Criteria:

• No source files found
• Unable to count lines

SKIP Criteria:

• Empty repository

---

7. 近期变更统计 (Recent Changes) — FAST

Purpose: Analyze lines added/deleted in recent commits to gauge development activity

Check Instructions:

# Lines changed in last 7 days (total summary)
git log --since="7 days ago" --oneline --stat | grep -E "file changed|files changed" | awk '{ins+=$4; del+=$6} END {printf "Last 7 days: +%d -%d (net %d)\n", ins, del, ins-del}'

# Per-commit breakdown for recent commits (last 10)
git log --since="7 days ago" --oneline --shortstat | head -30

# Lines changed in last 30 days (total summary)
git log --since="30 days ago" --oneline --stat | grep -E "file changed|files changed" | awk '{ins+=$4; del+=$6} END {printf "Last 30 days: +%d -%d (net %d)\n", ins, del, ins-del}'

# Commit frequency
echo "Commits in last 7 days: $(git log --since='7 days ago' --oneline | wc -l)"
echo "Commits in last 30 days: $(git log --since='30 days ago' --oneline | wc -l)"

# Top changed files in last 7 days
git diff --stat HEAD~10..HEAD 2>/dev/null | tail -1
git log --since="7 days ago" --pretty=format: --name-only | sort | uniq -c | sort -rn | head -10

PASS Criteria:

• Recent commits with meaningful changes detected (7-day activity)
• Net lines of change reported successfully

WARN Criteria:

• No commits in last 7 days but activity within 30 days
• Very high churn (> 5,000 lines changed in 7 days) may indicate instability

FAIL Criteria:

• No commits in last 30 days
• Unable to compute change statistics

SKIP Criteria:

• Not a git repository
• Fewer than 2 commits in history

---

8. 测试覆盖矩阵 (Test Coverage Matrix) — FAST / FULL

Purpose: Map source modules to their test coverage across unit, integration, and E2E levels. FAST mode uses file-naming conventions; FULL mode runs coverage tools for precise line-level data.

FAST Mode — File Mapping

Scans source directories and checks for corresponding test files using naming conventions. No dependencies required.

Check Instructions:

# ---- Node.js / TypeScript ----
if [ -f "package.json" ]; then
  echo "=== Unit Tests ==="
  find src/ -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" \) \
    -not -name "*.test.*" -not -name "*.spec.*" -not -name "*.d.ts" 2>/dev/null | while read f; do
    base=$(basename "$f" | sed 's/\.[^.]*$//')
    dir=$(dirname "$f")
    # Check common test file locations
    unit=$(find . -type f \( -path "*/tests/*" -o -path "*/test/*" -o -path "*/__tests__/*" \) \
      -name "${base}.test.*" -o -name "${base}.spec.*" 2>/dev/null | head -1)
    if [ -n "$unit" ]; then
      echo "  ✅ $f → $unit"
    else
      echo "  ❌ $f (no unit test)"
    fi
  done

  echo "=== Integration Tests ==="
  find . -path "*/tests/integration/*" -o -path "*/test/integration/*" \
    -type f \( -name "*.test.*" -o -name "*.spec.*" \) 2>/dev/null | while read f; do
    echo "  ✅ $f"
  done

  echo "=== E2E Tests ==="
  find . -path "*/tests/e2e/*" -o -path "*/test/e2e/*" -o -path "*/e2e/*" \
    -type f \( -name "*.test.*" -o -name "*.spec.*" \) 2>/dev/null | while read f; do
    echo "  ✅ $f"
  done
fi

# ---- Python ----
if [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; then
  echo "=== Unit Tests ==="
  find . -name "*.py" -not -path "./venv/*" -not -path "./.venv/*" \
    -not -name "test_*" -not -name "*_test.py" -not -path "*/tests/*" 2>/dev/null | while read f; do
    base=$(basename "$f" .py)
    dir=$(dirname "$f")
    unit=$(find . -path "*/tests/*" \( -name "test_${base}.py" -o -name "${base}_test.py" \) 2>/dev/null | head -1)
    if [ -n "$unit" ]; then
      echo "  ✅ $f → $unit"
    else
      echo "  ❌ $f (no unit test)"
    fi
  done

  echo "=== Integration Tests ==="
  find . -path "*/tests/integration/*" -name "*.py" 2>/dev/null | while read f; do
    echo "  ✅ $f"
  done

  echo "=== E2E Tests ==="
  find . -path "*/tests/e2e/*" -o -path "*/tests/end_to_end/*" \
    -name "*.py" 2>/dev/null | while read f; do
    echo "  ✅ $f"
  done
fi

# ---- Go ----
if [ -f "go.mod" ]; then
  echo "=== Unit Tests ==="
  find . -name "*.go" -not -path "./vendor/*" -not -name "*_test.go" 2>/dev/null | while read f; do
    dir=$(dirname "$f")
    base=$(basename "$f" .go)
    testfile="${dir}/${base}_test.go"
    if [ -f "$testfile" ]; then
      echo "  ✅ $f → $testfile"
    else
      # Check for package-level test file
      pkgtst=$(find "$dir" -maxdepth 1 -name "*_test.go" 2>/dev/null | head -1)
      if [ -n "$pkgtst" ]; then
        echo "  ⚠️  $f → $pkgtst (package-level, not file-specific)"
      else
        echo "  ❌ $f (no test)"
      fi
    fi
  done

  echo "=== Integration Tests ==="
  find . -name "*_test.go" -not -path "./vendor/*" \
    -exec grep -l "// +build integration\|//go:build integration" {} \; 2>/dev/null | while read f; do
    echo "  ✅ $f"
  done
fi

# ---- Rust ----
if [ -f "Cargo.toml" ]; then
  echo "=== Unit Tests ==="
  find src/ -name "*.rs" 2>/dev/null | while read f; do
    has_test=$(grep -c "#\[test\]" "$f" 2>/dev/null)
    if [ "$has_test" -gt 0 ]; then
      echo "  ✅ $f ($has_test tests)"
    else
      echo "  ❌ $f (no #[test])"
    fi
  done

  echo "=== Integration Tests ==="
  find tests/ -name "*.rs" 2>/dev/null | while read f; do
    echo "  ✅ $f"
  done
fi

# ---- Summary: uncovered modules ----
echo ""
echo "=== Uncovered Source Files ==="
# Count files without tests (re-run logic, count only)

PASS Criteria:

• ≥ 80% of source files have corresponding unit test files
• At least one integration or E2E test suite exists (if applicable)

WARN Criteria:

• 50-79% of source files have unit tests
• Missing integration or E2E tests entirely

FAIL Criteria:

• < 50% of source files have unit tests
• No test files found at all

FULL Mode — Coverage Tool Analysis

Runs existing coverage tools to get precise line-level coverage data, aggregated by module/directory.

Check Instructions:

# ---- Node.js / TypeScript ----
if [ -f "package.json" ]; then
  # Check if coverage tool is available (jest/vitest have it built-in)
  npx jest --coverage --coverageReporters=text-summary 2>&1 | tail -20 || \
  npx vitest run --coverage 2>&1 | tail -20 || \
  echo "NO_COVERAGE_TOOL"

  # Per-directory coverage (if jest)
  npx jest --coverage --coverageReporters=text 2>&1 | grep -E "^\s*(src/|All files)" | head -30
fi

# ---- Python ----
if [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; then
  # pytest-cov provides per-module coverage
  python -m pytest --cov=. --cov-report=term-missing 2>&1 | grep -E "^src/|^app/|^TOTAL" | head -30 || \
  echo "NO_COVERAGE_TOOL: install pytest-cov"
fi

# ---- Go ----
if [ -f "go.mod" ]; then
  # Built-in coverage with per-function breakdown
  go test ./... -cover -coverprofile=coverage.out 2>&1
  go tool cover -func=coverage.out 2>&1 | tail -30
  rm -f coverage.out
fi

# ---- Rust ----
if [ -f "Cargo.toml" ]; then
  # Requires cargo-tarpaulin or cargo-llvm-cov
  cargo tarpaulin --out Stdout 2>&1 | tail -20 || \
  cargo llvm-cov --summary-only 2>&1 | tail -20 || \
  echo "NO_COVERAGE_TOOL: install cargo-tarpaulin or cargo-llvm-cov"
fi

PASS Criteria:

• Overall line coverage ≥ 80%
• No module below 50% coverage
• Coverage data successfully generated

WARN Criteria:

• Overall coverage 60-79%
• 1-3 modules below 50% coverage
• Some modules have 0% coverage

FAIL Criteria:

• Overall coverage < 60%
• Many modules below 50% coverage
• Coverage tool fails to run

SKIP Criteria (both modes):

• No source files detected
• FULL mode only: no coverage tool available for the detected project type

---

9. 构建验证 (Build Verification) — FULL

Purpose: Verify project builds successfully

Check Instructions:

# Project-type specific build commands
if [ -f "package.json" ]; then
  npm run build 2>&1 || yarn build 2>&1 || pnpm build 2>&1
elif [ -f "Cargo.toml" ]; then
  cargo build --release 2>&1
elif [ -f "go.mod" ]; then
  go build ./... 2>&1
elif [ -f "pyproject.toml" ] || [ -f "setup.py" ]; then
  python -m build 2>&1 || pip install -e . 2>&1
elif [ -f "Makefile" ]; then
  make build 2>&1
fi

PASS Criteria:

• Build completes successfully (exit code 0)
• No build warnings or errors

WARN Criteria:

• Build completes but with warnings
• Build takes longer than expected (> 2 minutes)

FAIL Criteria:

• Build fails with errors
• No build command found

SKIP Criteria:

• Fast mode (not running full checks)

---

10. 单元测试 (Unit Tests) — FULL

Purpose: Verify unit tests pass and meet coverage thresholds

Check Instructions:

# Project-type specific test commands
if [ -f "package.json" ]; then
  npm test -- --coverage 2>&1 || yarn test --coverage 2>&1 || pnpm test --coverage 2>&1
  # Check coverage threshold (80%)
  cat coverage/coverage-summary.json 2>/dev/null | grep -o '"total".*"pct":[0-9.]*' || echo "No coverage data"
elif [ -f "Cargo.toml" ]; then
  cargo test 2>&1
  # Check coverage with tarpaulin if available
  cargo tarpaulin --out Stdout 2>&1 || echo "Coverage tool not installed"
elif [ -f "go.mod" ]; then
  go test ./... -cover 2>&1
elif [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; then
  python -m pytest --cov=. --cov-report=term-missing 2>&1
fi

PASS Criteria:

• All tests pass (exit code 0)
• Coverage ≥ 80% (if coverage data available)
• No skipped tests (or minimal skipped tests)

WARN Criteria:

• All tests pass but coverage 60-79%
• 1-5 tests skipped
• Some tests have long duration (> 1s each)

FAIL Criteria:

• One or more tests fail
• Coverage < 60%
• Many tests skipped (≥ 10)

SKIP Criteria:

• Fast mode (not running full checks)
• No test command found

---

11. E2E 测试 (E2E Tests) — FULL

Purpose: Verify end-to-end tests pass

Check Instructions:

# Project-type specific E2E test commands
if [ -f "package.json" ]; then
  npm run test:e2e 2>&1 || yarn test:e2e 2>&1 || pnpm test:e2e 2>&1 || npm run test:integration 2>&1
elif [ -f "Cargo.toml" ]; then
  cargo test --test '*' 2>&1
elif [ -f "go.mod" ]; then
  go test ./... -tags=integration 2>&1 || go test ./... -tags=e2e 2>&1
elif [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; then
  python -m pytest tests/e2e/ -v 2>&1 || python -m pytest tests/integration/ -v 2>&1
fi

PASS Criteria:

• All E2E tests pass (exit code 0)
• No timeouts or flaky test failures

WARN Criteria:

• All E2E tests pass but with warnings
• Some tests have long duration (> 10s each)

FAIL Criteria:

• One or more E2E tests fail
• Test suite times out
• No E2E test command found but E2E tests directory exists

SKIP Criteria:

• Fast mode (not running full checks)
• No E2E tests found (no tests/e2e/, tests/integration/, or test:e2e script)

---

12. 依赖健康 (Dependency Health) — FULL

Purpose: Audit dependencies for security vulnerabilities and outdated packages

Check Instructions:

# Project-type specific dependency audit
if [ -f "package.json" ]; then
  npm audit 2>&1 || yarn audit 2>&1 || pnpm audit 2>&1
  npm outdated 2>&1 || yarn outdated 2>&1 || pnpm outdated 2>&1
elif [ -f "Cargo.toml" ]; then
  cargo audit 2>&1 || cargo outdated 2>&1
  cargo update --dry-run 2>&1
elif [ -f "go.mod" ]; then
  go list -u -m all 2>&1
  go mod tidy 2>&1
elif [ -f "pyproject.toml" ] || [ -f "requirements.txt" ]; then
  pip-audit 2>&1 || safety check 2>&1
  pip list --outdated 2>&1
fi

PASS Criteria:

• No security vulnerabilities found
• No outdated dependencies (or only patch versions outdated)
• Dependency resolution successful

WARN Criteria:

• Low-severity vulnerabilities found
• 1-5 dependencies outdated (minor versions)
• Some dependencies have deprecation warnings

FAIL Criteria:

• High or critical severity vulnerabilities found
• Many dependencies outdated (≥ 10)
• Dependency resolution fails

SKIP Criteria:

• Fast mode (not running full checks)
• No package manager detected

---

Report Format

Generate a Markdown report with the following structure:

# Project Health Check Report

**Date:** [current date]
**Mode:** Fast / Full
**Project Type:** [detected type: Node.js / Rust / Go / Python / Other]
**Branch:** [current branch]

## Summary

| Metric | Value |
|--------|-------|
| Checks Passed | [N]/[total] |
| Checks with Warnings | [N] |
| Checks Failed | [N] |
| Checks Skipped | [N] |
| Overall Status | ✅ PASS / ⚠️ WARN / ❌ FAIL |

## Check Results

### 1. 提交状态 (Commit Status)
**Status:** ✅ PASS / ⚠️ WARN / ❌ FAIL / ⏭️ SKIP

**Details:**
- Uncommitted changes: [yes/no]
- Last commit: [date/ago]
- Untracked files: [count]

**Suggestions:** [actionable recommendations]

### 2. 分支同步 (Branch Sync)
**Status:** ✅ PASS / ⚠️ WARN / ❌ FAIL / ⏭️ SKIP

**Details:**
- Ahead/behind remote: [commits ahead / behind]
- Stale branches: [count]

**Suggestions:** [actionable recommendations]

[... repeat for checks 3-5 ...]

### 6. 代码规模 (Code Size)
**Status:** ✅ PASS / ⚠️ WARN / ❌ FAIL / ⏭️ SKIP

**Details:**
- Total lines of code: [N]
- Total tracked files: [N]
- Language breakdown: [TypeScript: N, Python: N, ...]

**Suggestions:** [actionable recommendations]

### 7. 近期变更统计 (Recent Changes)
**Status:** ✅ PASS / ⚠️ WARN / ❌ FAIL / ⏭️ SKIP

**Details:**
- Last 7 days: [N commits, +N/-N lines (net: N)]
- Last 30 days: [N commits, +N/-N lines (net: N)]
- Top changed files: [list]

**Suggestions:** [actionable recommendations]

### 8. 测试覆盖矩阵 (Test Coverage Matrix)
**Status:** ✅ PASS / ⚠️ WARN / ❌ FAIL / ⏭️ SKIP
**Mode:** FAST (file mapping) / FULL (coverage tools)

**Details (FAST):**
| Module / Source File | unit | integration | e2e |
|----------------------|------|-------------|-----|
| src/auth/login.ts | ✅ | ✅ | ❌ |
| src/auth/register.ts | ✅ | ❌ | ❌ |
| src/payment/checkout.ts | ❌ | ❌ | ❌ |

Coverage: [N]/[M] files have unit tests ([%]%)

**Details (FULL, if available):**
| Module | Lines | Covered | Coverage |
|--------|-------|---------|----------|
| src/auth | 120 | 108 | 90% |
| src/payment | 85 | 34 | 40% |
| **Total** | **205** | **142** | **69%** |

**Suggestions:** [actionable recommendations]

[... repeat for checks 9-12 (Full mode only) ...]

## Recommendations

### High Priority
- [Critical issues requiring immediate attention]

### Medium Priority
- [Important issues to address soon]

### Low Priority
- [Nice-to-have improvements]

## Next Steps

1. [Specific action item 1]
2. [Specific action item 2]
3. [Specific action item 3]

---

Project Adaptation

The health check automatically detects the project type and selects appropriate commands:

Node.js Projects

• Detection: package.json present
• Build: npm run build / yarn build / pnpm build
• Test: npm test / yarn test / pnpm test
• Coverage: --coverage flag (Jest/Vitest)
• Audit: npm audit / yarn audit / pnpm audit
• Outdated: npm outdated / yarn outdated / pnpm outdated

Rust Projects

• Detection: Cargo.toml present
• Build: cargo build --release
• Test: cargo test
• Coverage: cargo tarpaulin (if installed)
• Audit: cargo audit / cargo outdated
• Update Check: cargo update --dry-run

Go Projects

• Detection: go.mod present
• Build: go build ./...
• Test: go test ./... -cover
• E2E: go test ./... -tags=integration or -tags=e2e
• Outdated: go list -u -m all
• Tidy: go mod tidy

Python Projects

• Detection: pyproject.toml, requirements.txt, or setup.py present
• Build: python -m build or pip install -e .
• Test: python -m pytest --cov=. --cov-report=term-missing
• E2E: pytest tests/e2e/ or tests/integration/
• Audit: pip-audit or safety check
• Outdated: pip list --outdated

Generic Projects

• Detection: No package manager detected
• Build: Check for Makefile with build target
• Test: Check for Makefile with test target
• Documentation: Always run Fast mode checks

---

Status Definitions

Status	Meaning	Action Required
✅ PASS	Check completed successfully with no issues	None
⚠️ WARN	Check completed but found minor issues	Review and address when convenient
❌ FAIL	Check failed with significant issues	Address before next release
⏭️ SKIP	Check was skipped (not applicable or mode-dependent)	None

---

Usage Examples

Fast mode (default):

/health-check
Run a health check
Check project health

Full mode:

/health-check full
Run a full health check
Check project health with build and tests

Specific checks:

Check commit status and branch sync
Verify documentation completeness
Run dependency audit