doc-it-env

Name: doc-it-env
Availability: InStock
Author: tsuji-tomonori

Generate and revise IT-ENV documents compliant with diopside Obsidian standards.

1|Updated Feb 11, 2026

Search Tags:#testing #documentation #compliance #obsidian #diopside #it-env

Ready to run

npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-it-env

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-it-env
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-it-env
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-it-env

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 new or revised IT-ENV (Integration Test Environment) documents strictly adhere to the diopside Obsidian operational guidelines, maintaining consistency and quality.

Core Features & Use Cases

Standardized Document Creation: Generates IT-ENV documents (IT-ENV-*.md) that meet all diopside frontmatter and structural requirements.
Compliance Enforcement: Validates that documents align with the IT phase and environment-specific content guidelines.
Use Case: When setting up a new integration test environment, use this Skill to create the official documentation for its prerequisites, dependencies, and recovery procedures, ensuring it's immediately compliant with project standards.

Quick Start

Use the doc-it-env skill to create a new document for the integration test environment.

Frequently Asked Questions about doc-it-env

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

FAQPage Schema

How do I create integration test environment documentation that meets Obsidian frontmatter requirements?▼

Integration test environment documentation requires strict frontmatter and structural adherence to diopside Obsidian operational standards. Using a compliance-focused generation tool ensures documents meet IT phase content guidelines, validate internal links, and convert glossary terms automatically.

What are the diopside content guidelines for IT-ENV documents?▼

Diopside content guidelines for IT-ENV documents mandate specific frontmatter fields, IT phase content structures, and project-specific naming conventions. Adherence ensures that prerequisites, dependencies, and recovery procedures are consistently documented across the test environment.

How do I validate links and glossary terms in Obsidian vault documentation?▼

To validate links and glossary terms in Obsidian vault documentation, run automated validation scripts. These scripts check internal link integrity and automatically convert glossary terms to ensure terminology consistency across all integration test environment documents.

Does this document generation process support custom naming conventions for integration test environments?▼

Yes, the document generation process supports custom naming conventions for integration test environments. It enforces project-specific naming rules during the creation and revision of IT-ENV markdown files to maintain strict operational compliance.

What is the best way to ensure compliance when revising existing IT phase documents?▼

The best way to ensure compliance when revising existing IT phase documents is to use an automated validation and revision tool. It checks frontmatter requirements, enforces content guidelines, and performs glossary term conversion to align with diopside Obsidian standards.