Skill Change Verification - QA Skill Library

Why this Skill

It turns this Skill's method into a quality input that can be executed, reviewed, and reused.

Use this Skill when its method fits the current quality task.

When to use

Use this Skill

Use this Skill when its method fits the current quality task.

Common pitfalls

No content is available for this Skill yet.

Input

Minimum Input

Classify content, metadata/directory, script, Eval, and runtime impact.

Recommended Input

Project goal
Test scope
Constraints

Optional Context

Relevant code or configuration
Historical results
Logs and metrics

Output

The output follows this Skill's method and makes facts, assumptions, risks, and next steps explicit.

Judge the output value before installing

01Classify content, metadata/directory, script, Eval, and runtime impact.
02Select static, structural, evaluation, runtime, and human-review evidence.
03Record commands run, results, omitted checks, and reasons.
04Report residual risks and claims that are and are not supported.

How It Works

01Classify content, metadata/directory, script, Eval, and runtime impact.
02Select static, structural, evaluation, runtime, and human-review evidence.
03Record commands run, results, omitted checks, and reasons.
04Report residual risks and claims that are and are not supported.

Install & Quick Start

Install command / SHELL

npx skills add \
  https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/skill-engineering/skill-change-verification
  -g

skill-change-verification.prompt

@skill skill-change-verification

Using the current project context, produce an actionable result following this Skill.

Additional context:
[Paste project context or requirement]

---
name: skill-change-verification
description: Use this skill when selecting and reporting verification for Skill changes; triggers include Skill change verification, quality gates, and evidence levels.
---

# Skill Change Verification

Use this Skill to select the smallest sufficient checks for a change and state exactly what the evidence supports.

## Workflow

1. Classify content, metadata/directory, script, Eval, and runtime impact.
2. Select static, structural, evaluation, runtime, and human-review evidence.
3. Record commands run, results, omitted checks, and reasons.
4. Report residual risks and claims that are and are not supported.

## Constraints

- `skill-up validate` is not runtime semantic validation.
- Mark undiscoverable commands as confirmation items; never guess.
- Cover the actual diff instead of hiding gaps behind a full-suite run.

Read `prompts/skill-change-verification.md` before producing a report.