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

doc-ut-stat

Create and revise UT-STAT-*.md static analysis documentation for the diopside project.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that documentation for static analysis in unit testing (UT-STAT) adheres to the diopside documentation standards, making it easier to manage and understand.

Core Features & Use Cases

  • Standardized Documentation: Creates and updates UT-STAT documents following Obsidian operational rules.
  • Rule Management: Helps define static analysis rules, execution conditions, and pass/fail criteria.
  • Use Case: When adding a new ESLint rule to the project, use this Skill to create the corresponding UT-STAT document, detailing the rule's scope, execution command, and how failures are handled.

Quick Start

Use the doc-ut-stat skill to create a new document for the static analysis rule 'no-unused-vars'.

Frequently Asked Questions about doc-ut-stat

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

FAQPage Schema
How do I create standardized static analysis documentation for unit testing?▼

Static analysis documentation for unit testing is created by following Obsidian operational rules to define rule scope, execution commands, and pass/fail criteria in UT-STAT markdown files. This ensures adherence to project-specific documentation guidelines.

What should be included in a UT-STAT document for a new ESLint rule?▼

A UT-STAT document for a new ESLint rule should include the rule's scope, execution command, and how failures are handled. This standardizes static analysis configurations within the unit testing phase.

How do I manage static analysis rules in Obsidian?▼

Manage static analysis rules in Obsidian by creating and updating UT-STAT documents that define rule scope, execution conditions, and pass/fail criteria. This aligns configurations with project documentation standards.

Can I use this for updating existing static analysis documentation?▼

Updating existing static analysis documentation is supported by revising UT-STAT files to adhere to Obsidian operational rules. This manages rule scope, execution commands, and pass/fail criteria during revisions.

Does this work with the diopside project documentation standards?▼

This standardizes UT-STAT documentation specifically for the diopside project, ensuring static analysis documentation in unit testing adheres to project-specific Obsidian operational rules and guidelines.

What are the limitations of managing static analysis docs with UT-STAT?▼

UT-STAT documentation management is limited to static analysis within the unit testing phase for the diopside project. It focuses on rule scope, execution commands, and pass/fail criteria in Obsidian markdown files.

Related Skills

Explore More Software Engineering Skills→
tsuji-tomonoritsuji-tomonori

doc-ut-tdat

Generate and revise UT-TDAT Markdown documents per diopside project conventions.

Community
Intermediate
YokhanYokhan

test-rules

Automate regression testing of rule definitions from tests/rules/*.test.md files.

Community
Intermediate
tsuji-tomonoritsuji-tomonori

doc-ut-mock

Create and revise UT-MOCK documents following diopside Obsidian guidelines.

Community
Basic
shihwesleyshihwesley

obsidian-markdown

Create and edit Obsidian-flavored Markdown notes with wikilinks, embeds, and frontmatter.

Community
Intermediate