Files
Jonathan Miller 95880d3e44
Platform: mokocli CI / Gate 2: Unit Tests (8.1) (pull_request) Blocked by required conditions
Platform: mokocli CI / Gate 2: Unit Tests (8.2) (pull_request) Blocked by required conditions
Platform: mokocli CI / Gate 2: Unit Tests (8.3) (pull_request) Blocked by required conditions
Platform: mokocli CI / Gate 3: Self-Health Check (pull_request) Blocked by required conditions
Platform: mokocli CI / Gate 4: Governance (pull_request) Blocked by required conditions
Platform: mokocli CI / Gate 5: Template Integrity (pull_request) Blocked by required conditions
Platform: mokocli CI / CI Summary (pull_request) Blocked by required conditions
Universal: PR Check / Build RC Package (pull_request) Blocked by required conditions
Universal: PR Check / Report Issues (pull_request) Blocked by required conditions
Universal: PR Check / Branch Policy (pull_request) Successful in 1s
Universal: PR Check / Validate PR (pull_request) Failing after 5s
Universal: PR Check / Secret Scan (pull_request) Successful in 7s
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
Branch Cleanup / Delete merged branch (pull_request) Failing after 1s
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 14s
Platform: mokocli CI / Gate 1: Code Quality (pull_request) Failing after 53s
chore: complete namespace cleanup — remove all mokoplatform/MokoStandards/MokoEnterprise refs
390 files: templates, workflows, MCP servers, CLI tools, lib, deploy,
validate, wrappers, configs, docs. Pure find-and-replace.
2026-06-21 01:18:13 -05:00
..

Repository Structure Schemas

This directory contains template schema files for defining custom repository structures.

Overview

Schema files define the expected structure, files, and directories for different types of repositories in the Moko Consulting ecosystem.

Available Schemas

template-repository-structure.xml

A base template schema that can be customized for new repository types. This template includes:

  • Required root-level files (README, LICENSE, CHANGELOG, etc.)
  • Core directory structure (docs, scripts, .github)
  • Basic GitHub Actions workflow requirements
  • Documentation standards

Usage

To create a custom schema:

  1. Copy template-repository-structure.xml to your desired location
  2. Update the <metadata> section with your repository type details
  3. Customize the <root-files> and <directories> sections
  4. Reference appropriate templates from the /templates/ directory
  5. Save with a descriptive name (e.g., my-project-type.xml)

Schema Structure

Each schema file contains:

  • Metadata: Repository type, platform, maintainer information
  • Root Files: Required files in the repository root
  • Directories: Required and optional directory structure
  • Files within Directories: Specific files expected in each directory

Requirement Status Values

  • required: Must be present
  • suggested: Recommended but optional
  • optional: Nice to have
  • not-allowed: Should not be present

Template References

Use the <template> element to reference template files:

<file extension="md">
  <name>README.md</name>
  <template>templates/docs/required/template-README.md</template>
</file>

Always Overwrite Flag

Use <always-overwrite>false</always-overwrite> to protect files from being overwritten during sync:

<file extension="gitignore">
  <name>.gitignore</name>
  <always-overwrite>false</always-overwrite>
</file>
  • Schema validation: /scripts/validate/validate_structure_v2.py
  • Auto-detection: /scripts/validate/auto_detect_platform.php
  • Main schemas: /schemas/structures/