network-config-validation

Topics in the source

• Network Config Validation
• When to Use
• How It Works
• Dangerous Command Detection
• Duplicate IPs And Subnet Overlaps
• Management-Plane Checks
• Security Hygiene Checks
• Examples

Use this skill to review network configuration before a change window or before an automation run touches production devices. Reviewing Cisco IOS or IOS-XE style snippets before deployment. Auditing generated config from scripts or templates. Looking for dangerous commands, duplicate IP addresses, or subnet overlaps. Checking whether ACLs, route-maps, prefix-lists, or line policies are referenced but not defined. Building lightweight pre-flight scripts for network automation. Treat config validation as layered evidence, not as a complete parser. Regex checks are useful for pre-flight warnings, but final approval still needs a network engineer to review intent, platform syntax, and rollback steps. Validate in this order: 1. Destructive commands. 2. Credential and management-plane exposure. 3. Duplicate addresses and overlapping subnets. 4. Stale references to ACLs, route-maps, prefix-lists, and interfaces. 5. Operational hygiene such as NTP, timestamps, remote logging, and banners. Parse VTY blocks by section so access-class checks do not spill across unrelated lines. 1. Run dangerous-command checks on the exact snippet to be pasted. 2. Run duplicate IP and subnet overlap checks aga

This is an excerpt. Refer to the complete source and its current requirements.