verify-implementation

Automate post-change verification with preflight checks, targeted tests, and manual validation.

13|2|Updated Nov 16, 2025
One-click install
npx skills add https://github.com/rstacruz/agentic-toolkit --skill verify-implementation-rstacruz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-implementation
Source: https://github.com/rstacruz/agentic-toolkit/tree/main/skill/atk/verify-implementation
Command: npx skills add https://github.com/rstacruz/agentic-toolkit --skill verify-implementation-rstacruz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After code changes, verification ensures correctness by guiding automated checks and manual validation within the implementation workflow.

Core Features & Use Cases

  • Preflight checks: linting, formatting, and type-checking to catch issues early.
  • Targeted automated tests: run unit/integration tests focused on changed areas to validate behavior.
  • Manual verification: CLI output, UI checks, and QA validation with artefacts captured for traceability.

Quick Start

Run preflight checks, execute targeted tests for changed areas, and perform manual UI verification to complete the verification workflow.

Frequently Asked Questions about verify-implementation

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

FAQPage Schema
How do I automate verification after code changes to ensure correctness?

Automate verification after code changes by running preflight linting and type-checks, executing targeted tests for changed areas, and performing manual UI validation with artefact capture to ensure implementation integrity.

What is a preflight check workflow for code changes?

A preflight check workflow for code changes is a mandatory verification process that runs linting, formatting, and type-checking to catch issues early before executing targeted automated tests and manual validation.

How do I run targeted automated tests for changed code areas?

Run targeted automated tests for changed code areas by executing unit and integration tests focused on the modified sections to validate behavior and confirm implementation correctness within the verification workflow.

Does manual verification require artefact capture for traceability?

Manual verification requires artefact capture for traceability, validating implementation integrity through CLI output checks, UI validation, and QA processes to ensure correctness after code changes.

Can I use this verification workflow for both automated tests and manual UI checks?

This verification workflow supports both automated tests and manual UI checks, applying across post-change workflows including preflight checks, targeted tests, and manual validation to validate implementation integrity.

What's the best way to validate implementation integrity after code changes?

The best way to validate implementation integrity after code changes is a mandatory verification workflow combining preflight linting, targeted tests for changed areas, and manual validation with artefact capture for traceability.