change-verification

Capture baselines, analyze post-change diffs, and guide rollback decisions across Cisco IOS-XE/NX-OS, Juniper JunOS, and Arista EOS.

Updated Mar 15, 2026

Search Tags:#rollback #multi-vendor #diff-analysis #change-verification #network-automation #baseline-capture

Ready to run

npx skills add https://github.com/vahagn-madatyan/netsec-skills-suite --skill change-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-verification
Source: https://github.com/vahagn-madatyan/netsec-skills-suite/tree/main/skills/change-verification
Command: npx skills add https://github.com/vahagn-madatyan/netsec-skills-suite --skill change-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre/post change verification with baseline capture, diff analysis, and rollback decision guidance across Cisco IOS-XE/NX-OS, Juniper JunOS, and Arista EOS. Structured around a single change event lifecycle — before, during, and after — with impact classification and rollback criteria.

Core Features & Use Cases

Baseline capture before changes and structured post-change verification across Cisco IOS-XE/NX-OS, Juniper JunOS, and Arista EOS.
Deterministic diff analysis that classifies deviations as intended, side effects, or unexpected issues, with rollback criteria.
Stepwise change lifecycle guidance (before, during, after) including rollback planning and soak period recommendations.
Use Case: for planned maintenance, upgrades, or policy changes, to ensure changes converge to the expected state and to enable rapid rollback if needed.

Quick Start

Run the Change Verification workflow on a planned change to confirm baselines, post-change diffs, and rollback readiness.

Frequently Asked Questions about change-verification

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

FAQPage Schema

How do I perform pre and post change verification for network device upgrades?▼

Pre and post change verification involves capturing baselines before maintenance, performing deterministic diff analysis afterward, and guiding rollback decisions. This workflow applies to Cisco IOS-XE/NX-OS, Juniper JunOS, and Arista EOS network changes.

What is the best way to analyze network configuration diffs after a planned change?▼

The best way to analyze network configuration diffs is using a deterministic diff analysis that classifies deviations as intended changes, side effects, or unexpected issues. This structured approach evaluates post-change state against baselines to determine rollback readiness.

Does change verification support multi-vendor environments with Cisco, Juniper, and Arista?▼

Yes, change verification supports multi-vendor environments across Cisco IOS-XE/NX-OS, Juniper JunOS, and Arista EOS. It captures baselines and performs post-change diffs uniformly across these platforms within a repeatable, auditable workflow.

How do I decide when to rollback a network configuration change?▼

Rollback decisions are guided by classifying post-change diff deviations as intended, side effects, or unexpected issues. If unexpected issues are found or safety checks fail, the workflow provides structured rollback criteria to restore the baseline state.

How does baseline capture work before network maintenance or software updates?▼

Baseline capture works by recording the structured state of network devices before planned maintenance, configuration changes, or software updates. This pre-change snapshot enables deterministic delta analysis to verify the post-change state converges to the expected result.

What are the limitations of using automated diff analysis for network change verification?▼

Automated diff analysis is limited by its dependency on accurate baseline capture and predefined rollback criteria. It cannot detect issues outside the captured configuration scope and requires structured safety checks to validate intended changes versus side effects.