Code Quality — Đánh giá sức khỏe codebase

Đo lường và phân tích chất lượng code: health score, technical debt, complexity metrics.

Cập nhật bộ mới: /health (code quality dashboard 0-10), /tech-debt (debt register), /ck-code-review (code review automation).

Cú pháp

/code-health                       # Đánh giá tổng thể codebase
/debt-analysis                     # Phân tích technical debt chi tiết
/health                           # Code quality dashboard (0-10)
/tech-debt                        # Debt register + prioritization
/ck-code-review                   # Automated code review

Bảng tham chiếu nhanh

Lệnh	Mô tả	Output
`/code-health`	Quality metrics, test coverage, docs, maintainability	Health score 0-100
`/debt-analysis`	Tech debt identification, prioritization, refactoring roadmap	Debt report + roadmap

/code-health — Codebase Health

Bước 1: Scan metrics

Đo: test coverage, lint errors, type safety, complexity, duplication.

Bước 2: Assess quality

So sánh với thresholds. Score từ 0-100.

Bước 3: Report

Tổng hợp: strong points, weak areas, recommendations.

Health Score Breakdown:

Category	Weight	Metrics
Test Coverage	25%	Line, branch, function coverage
Type Safety	20%	TypeScript strictness, `any` count
Code Complexity	20%	Cyclomatic complexity, nesting depth
Documentation	15%	README, API docs, inline comments
Dependencies	10%	Outdated, vulnerable, unused deps
Maintainability	10%	File size, duplication, coupling

/debt-analysis — Technical Debt

/debt-analysis                     # Full analysis

Output:

Debt inventory: categorized list (architecture, code, test, docs, infra)
Prioritization: impact × effort matrix
Refactoring roadmap: phased plan with estimates

Ví dụ thực tế

/code-health output
/debt-analysis output

CODEBASE HEALTH: 72/100 (Good)
├── Test Coverage:    78% (target 80%) — WARN
├── Type Safety:      95% (2 `any` remaining) — GOOD
├── Complexity:       Low avg (3.2) — GOOD
├── Documentation:    45% — NEEDS WORK
├── Dependencies:     3 outdated, 1 vulnerable — WARN
└── Maintainability:  Good (low duplication)

TOP RECOMMENDATIONS:
1. Fix vulnerable dependency: lodash 4.17.20 → 4.17.21
2. Add API documentation (12 endpoints undocumented)
3. Increase test coverage: auth module only 45%

TECHNICAL DEBT INVENTORY
├── Architecture (High):
│   └── Monolith auth module needs extraction
├── Code (Medium):
│   ├── 3 God classes > 500 lines
│   └── Duplicate validation logic (orders + products)
├── Tests (Medium):
│   └── No integration tests for payment flow
└── Docs (Low):
    └── API reference outdated since v2 migration

PRIORITY: auth extraction > payment tests > God classes

Khi nào dùng / không dùng

Dùng	Không dùng
Đầu sprint — đánh giá code health	Giữa feature development
Plan refactoring sprint	Debug specific bug (dùng `/fix`)
Báo cáo cho stakeholders	Security audit (dùng `/security-audit`)

Skill bổ trợ

/health — Code quality dashboard (0-10)

Prefix: /health, /health --detailed, /health --trendsDashboard sức khỏe: coverage, complexity, duplication, maintainability score (0-10).

/health                       # Summary dashboard
/health --detailed            # Full metrics breakdown
/health --trends             # Trend analysis over time

Khi dùng: Đầu sprint, plan refactoring, executive reporting.

/tech-debt — Technical debt register

Prefix: /tech-debt, /tech-debt --register, /tech-debt --prioritizeIdentify + register tech debt: architecture, code, tests, docs. Prioritization matrix.

/tech-debt                    # Scan + identify
/tech-debt --register         # Create debt register
/tech-debt --prioritize       # Prioritization + roadmap

Khi dùng: Quarterly planning, after refactoring, before major changes.

/ck-code-review — Automated code review

Prefix: /ck-code-review, /ck-code-review <file>, /ck-code-review --fixAI-assisted code review: patterns, best practices, potential bugs.

/ck-code-review                # Review changed files
/ck-code-review src/api.ts    # Review specific file
/ck-code-review --fix         # Suggest fixes

Khi dùng: Before PR submission, quality gate, learning.

Bắt đầu

Quan trọng

AgentKit (AK) — Migration mới

Tham khảo

Dev — Bắt đầu

Dev — Lệnh chính

Dev — Phân tích & Nghiên cứu

Dev — Công cụ hỗ trợ

Dev — Skills nổi bật

QA — Bắt đầu

QA — Use Cases

PM — Bắt đầu

PM — Lập kế hoạch

PM — Vận hành

PM — Kỹ thuật

PM — Skills nổi bật

DevOps — Bắt đầu

DevOps — Triển khai

DevOps — Bảo mật & Chất lượng

DevOps — Giám sát

DevOps — Skills nổi bật

Design — Bắt đầu

Design — Công cụ

Design — Quy trình

Design — Skills nổi bật

Marketing — Bắt đầu

Marketing — Nội dung

Marketing — Phân phối

Marketing — Quản lý

Code Quality

Code Quality — Đánh giá sức khỏe codebase

Cú pháp

Bảng tham chiếu nhanh

/code-health — Codebase Health

/debt-analysis — Technical Debt

Ví dụ thực tế

Khi nào dùng / không dùng

Skill bổ trợ

​Code Quality — Đánh giá sức khỏe codebase

​Cú pháp

​Bảng tham chiếu nhanh

​/code-health — Codebase Health

​/debt-analysis — Technical Debt

​Ví dụ thực tế

​Khi nào dùng / không dùng

​Skill bổ trợ

Code Quality — Đánh giá sức khỏe codebase

Cú pháp

Bảng tham chiếu nhanh

/code-health — Codebase Health

/debt-analysis — Technical Debt

Ví dụ thực tế

Khi nào dùng / không dùng

Skill bổ trợ