Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

change-validation

Estrellas3

Forks2

Actualizado30 de junio de 2026 a las 12:51

Snapshot a node's state before and after a change, then report exactly what changed and whether the fabric is still healthy

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

wcollins

wcollins/skills-and-specs-lab

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Administradores de redes y sistemas informáticosOcupaciones informáticas y matemáticas·SOC 15-1244

SKILL.md

readonly

name	change-validation
description	Snapshot a node's state before and after a change, then report exactly what changed and whether the fabric is still healthy
state	draft

Change validation

Lab 1b solution and the second composable skill. Use this skill to wrap any network change in a pre/post check so you can prove the change did what you intended and broke nothing else. It composes device-state-query: same snapshot shape before and after, then a diff. This is the skill form of the smoke-test.sh discipline.

Scope

Validates the effect of one change on one or more named nodes. It does NOT make the change; the operator (or another skill) applies the change between the two snapshots. Read-only on both ends.

Steps

Pre-snapshot. For each node in scope, capture state using the device-state-query procedure. Store as before.
Hand back. Tell the operator the pre-snapshot is captured and to apply their change now. Wait for confirmation that the change is applied.
Post-snapshot. Capture the same nodes again. Store as after.
Diff. Compare before and after field by field:
- interfaces that changed oper state,
- BGP sessions that changed state (established -> not, or the reverse),
- new or removed neighbors.
Judge. The change is valid only when the intended difference appears AND no unintended regressions appear (no session that was established is now down, no interface that was up is now down, unless that was the stated intent).

Output

{
  "nodes": ["leaf1"],
  "intent": "<one line the operator gave>",
  "changed": [
    {"node": "leaf1", "field": "bgp[10.1.1.1].state", "before": "established", "after": "established"}
  ],
  "regressions": [],
  "valid": true,
  "summary": "Change applied. No regressions. 2/2 BGP sessions still established."
}

Failure modes

Operator never confirms the change: do not fabricate a post-snapshot; stop and report valid: false, reason: "change not confirmed".
Pre-snapshot itself unhealthy: warn loudly before the change; you cannot validate a change from a broken baseline. Suggest ./scripts/reset.sh.
A regression appears: set valid: false, list every regression, and recommend rollback. Never report valid: true with a non-empty regressions.

Más de este repositorio

mismo repositorio

device-state-query

wcollins/skills-and-specs-lab

Query one fabric node and return its interface and BGP state as structured JSON

2026-06-303

example-skill

wcollins/skills-and-specs-lab

Summarize a single piece of fabric state in a structured way, instead of returning a raw tool dump (replace this with your own one-line, verb-first description that says when to use the skill)

2026-06-303

contributing

wcollins/skills-and-specs-lab

Walk a workshop participant through contributing a skill or lab back to the Skills & Specs Lab via fork and pull request, including GitHub PAT setup

2026-06-213

network-state-query

wcollins/skills-and-specs-lab

Return a focused, structured health summary for one fabric node (interfaces and BGP), instead of a raw tool dump

2026-06-213

skills-creator

wcollins/skills-and-specs-lab

Scaffold a new agentskills.io SKILL.md from a short description, with the right frontmatter, a focused scope, and a quality checklist

2026-06-213

Change validation

Scope

Validates the effect of one change on one or more named nodes. It does NOT make the change; the operator (or another skill) applies the change between the two snapshots. Read-only on both ends.

Steps

Pre-snapshot. For each node in scope, capture state using the device-state-query procedure. Store as before.

Hand back. Tell the operator the pre-snapshot is captured and to apply their change now. Wait for confirmation that the change is applied.

Post-snapshot. Capture the same nodes again. Store as after.

Diff. Compare before and after field by field:

interfaces that changed oper state,
BGP sessions that changed state (established -> not, or the reverse),
new or removed neighbors.

Judge. The change is valid only when the intended difference appears AND no unintended regressions appear (no session that was established is now down, no interface that was up is now down, unless that was the stated intent).

Output

{ "nodes": ["leaf1"], "intent": "<one line the operator gave>", "changed": [ {"node": "leaf1", "field": "bgp[10.1.1.1].state", "before": "established", "after": "established"} ], "regressions": [], "valid": true, "summary": "Change applied. No regressions. 2/2 BGP sessions still established." }

Failure modes

Operator never confirms the change: do not fabricate a post-snapshot; stop and report valid: false, reason: "change not confirmed".

Pre-snapshot itself unhealthy: warn loudly before the change; you cannot validate a change from a broken baseline. Suggest ./scripts/reset.sh.

A regression appears: set valid: false, list every regression, and recommend rollback. Never report valid: true with a non-empty regressions.