agentleFS
Sign inStart free
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/metrics-dashboard-assistant/SKILL.md

metrics

Skill4 starsChanged 30 days agoMITView on GitHub

[UDS] Track development metrics, code quality indicators, and technical debt over time. Use when: assessing ongoing project health, classifying and trending technical debt, reporting code quality to a team. Not for: first-time assessment of an unfamiliar codebase — use /discover; test coverage specifically — use /coverage or /ac-coverage. Keywords: metrics, code quality, technical debt, project health, debt trend, 開發指標, 技術債, 專案健康度.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ingest, spec and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 3 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    test

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use --debt-trend to compare against previous snapshots.

    line 80
  2. Very specific:

    After /metrics completes, the AI assistant should suggest:

    line 149

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Metrics Dashboard Assistant | 開發指標助手

Track development metrics, code quality indicators, and project health over time.

追蹤開發指標、程式碼品質指示器，以及專案隨時間的健康狀態。

Usage | 使用方式

CommandPurpose用途
/metricsRun full project health check執行完整專案健康檢查
/metrics --qualityCode quality metrics only僅程式碼品質指標
/metrics --debtClassified technical debt report分類技術債報告
/metrics --debt-trendDebt trend over time技術債趨勢
/metrics --testTest health metrics測試健康指標
/metrics src/Scope to specific module限定特定模組範圍

Metric Categories | 指標類別

CategoryMetrics指標說明
Code QualityComplexity, duplication, lint warnings複雜度、重複率、lint 警告
Test HealthCoverage %, pass rate, flaky count覆蓋率 %、通過率、不穩定測試數
Commit QualitySize, frequency, conventional format大小、頻率、格式合規
Debt TrackingTODO/FIXME counts, age of issues, debt classificationTODO/FIXME 數量、問題存在時間、債務分類
Dependency HealthOutdated packages, vulnerability count過時套件、漏洞數量

Technical Debt Classification | 技術債分類

Based on SQALE methodology and ISO/IEC 25010 maintainability characteristics.

基於 SQALE 方法和 ISO/IEC 25010 維護性子特性。

CategoryWhat to Measure衡量項目Detection Method
Code DebtTODO/FIXME, dead code, duplicationsTODO/FIXME、死碼、重複Grep, lint
Test DebtUncovered modules, low coverage areas未覆蓋模組、低覆蓋區域Coverage report
Design DebtComplexity hotspots (cyclomatic > 15), deep nesting複雜度熱點、深層巢狀Static analysis
Doc DebtUndocumented APIs, outdated docs未文件化 API、過時文件JSDoc/TypeDoc scan
Dependency DebtOutdated packages, known CVEs過時套件、已知 CVEnpm audit/outdated

Debt Report Format | 債務報告格式

## Technical Debt Report

**Date**: YYYY-MM-DD | **Debt Density**: N items per 1K lines

### Summary
| Category | Count | Severity | Est. Fix Time | Trend |
|----------|-------|----------|---------------|-------|
| Code Debt | 42 | Medium | 21h | ↑ +5 |
| Test Debt | 15 modules | High | 30h | → stable |
| Design Debt | 3 hotspots | High | 16h | ↓ -1 |
| Doc Debt | 8 APIs | Low | 8h | ↑ +2 |
| Dependency Debt | 5 outdated | Critical | 4h | → stable |

**Total Estimated Remediation**: 79 hours

### Top Priority Items
1. [CRITICAL] CVE-2024-XXXX in lodash — fix: npm update
2. [HIGH] src/parser/ complexity 28 — fix: extract methods
3. [HIGH] src/payments/ 0% coverage — fix: add IT tests

Trend Tracking | 趨勢追蹤

Use --debt-trend to compare against previous snapshots.

使用 --debt-trend 與過去的快照比較。

User: /metrics --debt-trend
AI: Technical Debt Trend (last 3 months):

    Code Debt:   ████████░░ 42 (+5)  ↑ increasing
    Test Debt:   ██████░░░░ 15 (0)   → stable
    Design Debt: ███░░░░░░░  3 (-1)  ↓ improving
    Doc Debt:    ████░░░░░░  8 (+2)  ↑ increasing
    Dep Debt:    ██░░░░░░░░  5 (0)   → stable

    Overall: 73 items (was 67) — ⚠️ debt increasing

Quick Health Score | 快速健康分數

The health score is a weighted composite:

健康分數為加權組合：

FactorWeightIdeal理想值
Test coverage30%>= 80%>= 80%
Lint pass rate20%100%100%
TODO/FIXME density15%< 1 per 1K lines< 每千行 1 個
Build success20%100%100%
Dependency freshness15%< 3 months< 3 個月

Score = sum(factor_score * weight)

Workflow | 工作流程

  1. COLLECT - Gather raw metrics from tools and git history
  2. ANALYZE - Compare against thresholds and historical trends
  3. REPORT - Generate summary with actionable highlights
  4. TREND - Show direction (improving / declining / stable)
  1. 收集 - 從工具與 git 歷史收集原始指標
  2. 分析 - 與閾值及歷史趨勢比較
  3. 報告 - 產生含可行動重點的摘要
  4. 趨勢 - 顯示方向（改善 / 衰退 / 穩定）

Usage Examples | 使用範例

User: /metrics
AI: Analyzing project health...
    Code Quality:  B+ (complexity avg 8.2, 0 lint errors)
    Test Health:   A  (coverage 87%, 0 flaky tests)
    Debt Tracking: C  (42 TODOs, 3 FIXMEs)
    Overall Score: 78/100 (Good)
User: /metrics --debt
AI: Technical Debt Summary:
    TODO:  42 (12 in src/legacy/, 8 in src/utils/)
    FIXME: 3  (all in src/parser/)
    Oldest: 6 months (src/legacy/auth.js:45)
    Trend:  +5 since last month (increasing)

Next Steps Guidance | 下一步引導

After /metrics completes, the AI assistant should suggest:

指標分析完成。建議下一步 / Metrics analysis complete. Suggested next steps:

  • 執行 /refactor 處理高複雜度模組 ⭐ Recommended / 推薦 — Address high-complexity modules
  • 執行 /coverage 改善低覆蓋率區域 — Improve low-coverage areas
  • 執行 /audit 檢視安全與依賴問題 — Review security & dependency issues
  • 執行 /metrics --debt-trend 追蹤技術債趨勢 — Track debt trend over time
  • 執行 /retrospective 在回顧中討論技術債 — Discuss tech debt in retrospective

Version History | 版本歷史

VersionDateChanges變更
1.1.02026-03-26Add tech debt classification, SQALE quantification, trend tracking新增技術債分類、SQALE 量化、趨勢追蹤
1.0.02026-03-24Initial release初始版本

AI Agent Behavior | AI 代理行為

完整的 AI 行為定義請參閱對應的命令文件：/metrics

For complete AI agent behavior definition, see the corresponding command file: /metrics

License | 授權

CC BY 4.0

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free