xddp.08.verify

Verify source code against CHD and CRS artifacts in XDDP workflows.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/tsuna44/XddpSettings --skill xddp-08-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xddp.08.verify
Source: https://github.com/tsuna44/XddpSettings/tree/main/ClaudeCode/.claude/skills/xddp.08.verify
Command: npx skills add https://github.com/tsuna44/XddpSettings --skill xddp-08-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of ensuring code quality and design consistency in XDDP-based development by automating the static verification process against Change Requirements (CRS) and Change Design (CHD) documents.

Core Features & Use Cases

  • Automated Static Verification: Executes consistent verification logic across multiple repositories to ensure code aligns with design specifications.
  • Cross-Repository Interface Validation: Detects implementation mismatches in cross-repository interfaces to prevent integration errors.
  • Use Case: After manually modifying code for a specific CR, trigger this skill to verify that the implementation still adheres to the defined architecture and requirements without needing to re-run the entire coding pipeline.

Quick Start

Execute the static verification process for the specified change request by running the command with the relevant CR number.

Frequently Asked Questions about xddp.08.verify

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

FAQPage Schema
How do I verify source code against design specifications in an XDDP workflow?

Static verification validates implementation consistency by comparing source code against Change Design (CHD) and Change Requirements (CRS) artifacts. It orchestrates sub-agents to detect coding errors and interface mismatches, providing clear feedback for remediation.

What is the best way to detect cross-repository interface mismatches after implementing a change request?

Cross-repository interface validation detects implementation mismatches across multiple repositories to prevent integration errors. It ensures code aligns with design specifications by executing consistent verification logic across all affected repositories.

Can I check code compliance against change requirements without re-running the entire coding pipeline?

Yes, after manually modifying code for a specific Change Request, you can trigger static verification to confirm the implementation adheres to defined architecture and requirements without re-running the entire coding pipeline.

How does static analysis ensure compliance with architecture in multi-repository development?

Static analysis ensures compliance by validating implementation consistency across single or multiple repositories, comparing code against CHD and CRS artifacts to detect coding errors and interface mismatches within the XDDP workflow.

What artifacts are required to perform static verification of code changes?

Static verification requires Change Design (CHD) and Change Requirements (CRS) artifacts to validate implementation consistency. The process compares source code against these artifacts to detect coding errors and interface mismatches.

When should I use automated static verification instead of manual code review?

Automated static verification is ideal after manually modifying code for a specific CR, ensuring implementation adheres to defined architecture without re-running the pipeline. It provides consistent verification logic across multiple repositories.