diff-artifacts

Classify input artifact elements as covered, partial, or dropped and write coverage-check.yaml.

3|Updated Jan 25, 2026

Search Tags:#drift detection #SDLC #traceability #requirements validation #coverage analysis #semantic comparison #artifact diff

Ready to run

npx skills add https://github.com/kapilvirenahuja/garura --skill diff-artifacts

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diff-artifacts
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/diff-artifacts
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill diff-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams verify whether an output artifact truly covers the required elements defined in an input artifact, while detecting dropped items and drifted additions.

Core Features & Use Cases

Model-reasoned element coverage: Extracts discrete input elements per a specified check_type and classifies each as covered, partial, or dropped using semantic reasoning.
Drift detection: Flags output content that is not traceable back to any input element to reveal scope creep or unanchored changes.
Coverage-check report generation: Writes a structured coverage-check.yaml summary including counts and a coverage_score.

Quick Start

Ask the judge agent to run diff-artifacts with input_path, output_path, check_type, and output_report_path to produce coverage-check.yaml.

Frequently Asked Questions about diff-artifacts

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

FAQPage Schema

How do I check semantic coverage and drift between SDLC artifacts?▼

To check semantic coverage and drift, supply input and output artifact paths along with a check type. The process extracts discrete input elements, classifies each as covered, partial, or dropped using model reasoning, and generates a structured coverage-check.yaml report.

What is requirements traceability validation and how does semantic comparison work?▼

Requirements traceability validation ensures output deliverables fully cover input specifications without unanchored drift. Semantic comparison uses model reasoning to evaluate element coverage rather than literal text matching, accurately identifying partial or dropped requirements across artifacts.

How do I generate a coverage analysis report for requirements validation?▼

Generate a coverage analysis report by providing input and output artifact paths. The system computes a coverage summary containing element counts, drift items, and a coverage score, then writes the results directly to a structured coverage-check.yaml file.

Can I detect dropped requirements and scope creep between design and build artifacts?▼

Yes, you can detect dropped requirements and scope creep by comparing design and build artifacts. The drift detection mechanism flags output content that is not traceable back to any input element, revealing unanchored changes or scope additions.

Does artifact diff use literal text matching to validate requirements coverage?▼

Artifact diff does not use literal text matching to validate requirements coverage. It applies model reasoning to perform semantic comparison, ensuring that paraphrased or structurally altered elements are correctly classified as covered, partial, or dropped.

What are the limitations of using semantic comparison for SDLC traceability?▼

A limitation of semantic comparison for SDLC traceability is its reliance on model reasoning, which may require clear input and output artifact paths. It produces a structured coverage-check.yaml report but depends on the specified check type to extract relevant elements.