skills.rest
usurobor
usuroborCOMMUNITY
Explore all skills by this author →
GitHub

review/diff-context

Validate diffs for structural integrity, cross-format parity, and execution timelines.

8|Updated Feb 2, 2026
Search Tags:#timeline#context#audit#structure#diff#code-review#parity
One-click install
npx skills add https://github.com/usurobor/cnos --skill review-diff-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review/diff-context
Source: https://github.com/usurobor/cnos/tree/main/src/packages/cnos.cdd/skills/cdd/review/diff-context
Command: npx skills add https://github.com/usurobor/cnos --skill review-diff-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-context inspection ensures diffs are auditable and coherent by validating structural closure, cross-format parity, and accurate execution timelines.

Core Features & Use Cases

  • Structural closure verification across input sources
  • Multi-format parity checks to align prose, JSON, YAML, and code blocks
  • Snapshot and stale-path validation to detect moves or renames
  • Derivation and authority-surface consistency checks across phases

Quick Start

Run this skill on the current diff to generate structured diff-context findings and actionable guidance.

Frequently Asked Questions about review/diff-context

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

FAQPage Schema
How do I validate code diffs for structural integrity during a code review?▼

Diff-context inspection validates structural closure, cross-format parity, and execution timelines to ensure diffs are auditable and coherent, outputting structured findings with severity and type to prevent regressions.

What does cross-format parity checking mean for patch diffs?▼

Cross-format parity checks align prose, JSON, YAML, and code blocks within patch diffs to ensure structural consistency, verifying that changes maintain derivation and authority-surface consistency.

How do I perform a change audit to detect stale paths and snapshot moves?▼

Run diff-context inspection on the current diff to validate snapshots and detect stale paths, identifying file moves or renames while enumerating input sources for structural closure.

Can I use diff-context inspection for contract walks across execution phases?▼

Yes, diff-context inspection supports contract walks across Phase 2a and Phase 2b by implementing Phase 2b constraints and verifying derivation and authority-surface consistency for execution timeline accuracy.

What is the best way to prevent regressions when reviewing diffs across multiple input sources?▼

Structural closure verification across input sources, combined with snapshot validation and timeline checks, prevents regressions by producing actionable findings with severity and confinement details.

Why does my diff pass review but still introduce timeline and parity regressions?▼

Diffs introduce regressions when structural closure, cross-format parity between prose, JSON, YAML, and code blocks, or execution timeline constraints are not validated against derivation and authority-surface consistency.

Related Skills

Explore More Software Engineering Skills→
MaxSaietsMaxSaiets

diffs

Generate unified diffs from before/after text or patch strings.

Community
Intermediate
flc1125flc1125
32

code-review

Review git-backed code changes and report findings by severity.

Community
Intermediate
D0NMEGAD0NMEGA
8

gsd-audit-uat

Audit UAT and verification items across project phases using path-globs.

Community
Advanced
refined-prunrefined-prun
35

review-pr

Review GitHub pull requests against project guidelines and produce a structured review artifact.

Official
Advanced