Verification Baseline (Core)
Purpose (Core)
Verification asks whether the complete candidate is internally consistent,
loadable, within scope, and capable of producing the intended effect without
obvious collateral damage. It is not permission to weaken the intended change
until a check passes.
Procedure (Core)
Before returning a change:
- Review the complete diff or update set. Remove unintended edits, debug text,
stale artifacts, no-op churn, and unrelated formatting.
- Confirm every changed unit is inside the declared mutation scope, every
declared unit actually changed, and every protected input is untouched.
- Trace dependencies and callers of shared surfaces. Preserve registration,
imports, defaults, signatures, schemas, side effects, and companion files
unless the diagnosis requires a coordinated change.
- Validate syntax and structure with the plugin's available checks. Confirm
the candidate loads through its real integration path, not only an isolated
parser.
- Inspect the final rendered or agent-visible form of prompts, descriptions,
templates, hooks, and schemas. Check placeholders, escaping, formatting,
examples, parameter names, and runtime behavior for consistency.
- Exercise empty inputs, boundary values, error paths, and representative
existing callers when they can reach the changed surface.
- Recheck behavior that already passed and could be affected. A targeted fix
should not silently broaden, suppress, or reorder unrelated behavior.
- Confirm the mutation is substantive: the effective candidate differs in
the intended way after normalization, rendering, or serialization.
- Return only when the proposed effect, actual changed units, verification
evidence, and structured result agree exactly.
Failure Handling (Core)
If verification fails, repair or remove the invalid change and rerun the same
check. Do not hide the failure, modify protected evaluation logic, fabricate a
successful result, or change intended semantics merely to satisfy a superficial
check. The plugin-specific verification skill may impose stricter rules; those
rules are part of the candidate contract.
1---2name: verification-baseline3description: "Use after applying a candidate change to verify its diff, scope, syntax, integration behavior, and consistency before returning it."4metadata:5 source: https://skillmd.com/skills/microsoft/verification-baseline6---78# Verification Baseline (Core)910## Purpose (Core)1112Verification asks whether the complete candidate is internally consistent,13loadable, within scope, and capable of producing the intended effect without14obvious collateral damage. It is not permission to weaken the intended change15until a check passes.1617## Procedure (Core)1819Before returning a change:20211. Review the complete diff or update set. Remove unintended edits, debug text,22 stale artifacts, no-op churn, and unrelated formatting.232. Confirm every changed unit is inside the declared mutation scope, every24 declared unit actually changed, and every protected input is untouched.253. Trace dependencies and callers of shared surfaces. Preserve registration,26 imports, defaults, signatures, schemas, side effects, and companion files27 unless the diagnosis requires a coordinated change.284. Validate syntax and structure with the plugin's available checks. Confirm29 the candidate loads through its real integration path, not only an isolated30 parser.315. Inspect the final rendered or agent-visible form of prompts, descriptions,32 templates, hooks, and schemas. Check placeholders, escaping, formatting,33 examples, parameter names, and runtime behavior for consistency.346. Exercise empty inputs, boundary values, error paths, and representative35 existing callers when they can reach the changed surface.367. Recheck behavior that already passed and could be affected. A targeted fix37 should not silently broaden, suppress, or reorder unrelated behavior.388. Confirm the mutation is substantive: the effective candidate differs in39 the intended way after normalization, rendering, or serialization.409. Return only when the proposed effect, actual changed units, verification41 evidence, and structured result agree exactly.4243## Failure Handling (Core)4445If verification fails, repair or remove the invalid change and rerun the same46check. Do not hide the failure, modify protected evaluation logic, fabricate a47successful result, or change intended semantics merely to satisfy a superficial48check. The plugin-specific verification skill may impose stricter rules; those49rules are part of the candidate contract.