agentleFS
Sign inStart free
AsiaOstrichAsiaOstrich/EngramGraph/.agents/skills/test-coverage-assistant/SKILL.md

coverage

Skill4 starsChanged 28 days agoMITView on GitHub

[UDS] Analyze code-level test coverage across the eight-dimension framework and recommend which gaps to close. Use when: coverage percentages look healthy but defects still ship, judging test completeness beyond line percentage, setting coverage targets. Not for: requirement-level AC-to-test traceability — use /ac-coverage; writing the missing tests — use /tdd or /spec-derive. Keywords: test coverage, eight dimensions, line coverage, branch coverage, test quality, 測試覆蓋率, 八維度, 測試完整性.

28 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use lint, profile and 2 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.
  • Microsoft AzureSkill

    lint

    Run all linting and spell checking for TypeScript and Rust code. Run this before committing to catch style issues, clippy warnings, and misspellings.

    Also in 4 projects that use this

  • julienamorganSkill

    profile

    Researches the user's market, competitors, and competitive positioning to build a complete ICP profile. Shows findings for user approval before proceeding. Triggers: /profile, "research my market", "who are my competitors". Reads: ./gtm/company.md, ./gtm/icp.md. Writes: updates ./gtm/icp.md with competitive positioning. Standalone: yes (asks for domain if company.md missing).

    Also in 3 projects that use this

  • MicrosoftSkill

    worktree

    Create, reuse or clean up a dedicated git worktree for working on a pull request or a private branch. Use from any PR-scoped workflow that needs an isolated checkout to keep current code and build output untouched.

    Also in 3 projects that use this

  • Google CloudSkill

    fix

    Plan a remediation strategy after a test failure.

    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, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Requirement Coverage: - All requirements have tests

    line 35
  2. Very specific:

    After /coverage completes, the AI assistant should suggest:

    line 70

“Common” is measured: kept by at least 6 in 10 of the 25 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

Test Coverage Assistant | 測試覆蓋率助手

Analyze test coverage across multiple dimensions and provide actionable recommendations.

多維度分析測試覆蓋率並提供可執行的建議。

Related: For requirement-level coverage (which AC have tests?), use /ac-coverage instead. This skill (/coverage) focuses on code-level coverage (lines, branches, functions).

相關：如需需求層級覆蓋率（哪些 AC 有對應測試？），請改用 /ac-coverage。此技能（/coverage）專注於程式碼層級覆蓋率。

Coverage Dimensions | 覆蓋率維度

DimensionWhat it Measures測量內容
LineLines of code executed執行的程式碼行數
BranchDecision paths taken決策路徑覆蓋
FunctionFunctions called呼叫的函數
StatementStatements executed執行的陳述式

8-Dimension Framework | 八維度框架

  1. Code Coverage - Lines, branches, functions
  2. Requirement Coverage - All requirements have tests
  3. Risk Coverage - High-risk areas prioritized
  4. Integration Coverage - Component interaction paths
  5. Edge Case Coverage - Boundary conditions tested
  6. Error Coverage - Error handling paths verified
  7. Permission Coverage - Access control scenarios
  8. AI Generation Quality - AI-generated test effectiveness

Coverage Targets | 覆蓋率目標

LevelCoverageUse Case適用場景
Minimum60%Legacy code遺留程式碼
Standard80%Most projects大多數專案
High90%Critical systems關鍵系統
Critical95%+Safety-critical安全關鍵

Workflow | 工作流程

  1. Run coverage tool - Generate coverage report | 產生覆蓋率報告
  2. Analyze gaps - Identify untested areas | 識別未測試區域
  3. Prioritize - Rank by risk and importance | 依風險排序
  4. Recommend tests - Suggest specific tests to add | 建議新增測試
  5. Track progress - Monitor coverage over time | 追蹤進度

Usage | 使用方式

/coverage                   - Run full coverage analysis | 執行完整覆蓋率分析
/coverage src/auth          - Analyze specific module | 分析特定模組
/coverage --recommend       - Get test recommendations | 取得測試建議

Next Steps Guidance | 下一步引導

After /coverage completes, the AI assistant should suggest:

覆蓋率分析完成。建議下一步 / Coverage analysis complete. Suggested next steps:

  • 覆蓋率不足 → 執行 /tdd 補齊測試 — Coverage gaps → Run /tdd to add tests
  • 已達標 → 執行 /checkin 品質關卡 ⭐ Recommended / 推薦 — Targets met → Run /checkin quality gates
  • 發現熱點 → 執行 /refactor 改善可測試性 — Hotspots found → Run /refactor

Reference | 參考

  • Detailed guide: guide.md
  • Core standard: test-completeness-dimensions.md

AI Agent Behavior | AI 代理行為

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

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

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