skills.rest
tsuji-tomonori
tsuji-tomonoriCOMMUNITY
Explore all skills by this author →
GitHub

doc-ut-cov

Create and revise UT-COV documents with standardized coverage thresholds and traceability.

1|Updated Feb 11, 2026
Search Tags:#testing#software engineering#documentation#unit test#coverage#diopside
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-ut-cov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-ut-cov
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-ut-cov
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-ut-cov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires auto_link_glossary.py, validate_vault.py, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that Unit Test Coverage (UT-COV) documentation within the diopside project adheres to a consistent standard for measurement conditions, thresholds, and exclusion justifications.

Core Features & Use Cases

  • Standardized Documentation: Creates and revises UT-COV documents (UT-COV-*.md) following project conventions.
  • Consistent Metrics: Ensures clarity on coverage thresholds, pass/fail criteria, and exclusion rationales.
  • Traceability: Maintains links to related design and integration documents.
  • Use Case: When updating the coverage report for a new feature, use this Skill to ensure the measurement methodology, acceptable thresholds, and any code exclusions are clearly documented and justified according to diopside's standards.

Quick Start

Use the doc-ut-cov skill to create or update the UT-COV document for the 'authentication module'.

Frequently Asked Questions about doc-ut-cov

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document unit test coverage thresholds and exclusion justifications consistently?▼

To standardize unit test coverage documentation, define measurement conditions, thresholds, pass/fail criteria, and exclusion rationales within UT-COV files while maintaining traceability to upstream design documents.

What is a UT-COV document and what should it include?▼

A UT-COV document standardizes unit test coverage reporting by detailing measurement methodology, acceptable coverage thresholds, pass/fail criteria, and links to related design and integration documents.

How do I create a unit test coverage report for a new feature module?▼

Create a UT-COV document for the new feature module by applying standardized frontmatter, documenting the measurement conditions, and justifying any code exclusions according to project conventions.

Does this coverage documentation process require links to upstream design documents?▼

Yes, the coverage documentation process requires traceability, ensuring UT-COV files maintain consistent links to related upstream design and integration documents for context and validation.

Why do I need to justify code exclusions in my unit test coverage report?▼

Justifying code exclusions in your unit test coverage report ensures transparency regarding why specific code paths are omitted from measurement, maintaining consistent evaluation standards across the project.

Related Skills

Explore More Software Engineering Skills→
tsuji-tomonoritsuji-tomonori

doc-dd-iam

Standardize DD-IAM infrastructure design documents for the diopside project.

Community
Intermediate
tsuji-tomonoritsuji-tomonori

doc-ut-case

Generate and revise Unit Test Case documents in Markdown for Obsidian.

Community
Intermediate
tsuji-tomonoritsuji-tomonori

obsidian-doc-change

Validate and correct frontmatter and Obsidian links in diopside docs.

Community
Intermediate
tsuji-tomonoritsuji-tomonori

obsidian-doc-check

Validate Obsidian markdown documents against project-specific conventions.

Community
Intermediate