When should I run the verification stack?

You should run the full stack whenever you modify runtime code, authentication flows, billing logic, build tools, or CI scripts to ensure no regressions were introduced.

Can I skip verification for small changes?

Verification can be skipped for documentation-only changes, comment-only changes, or formatting-only changes that do not affect runtime behavior.

What happens if a verification check fails?

If any part of the stack fails, the skill mandates that you fix the issue and re-run the entire stack until it passes before marking the task as complete.

Does this skill work on different operating systems?

Yes, it includes specialized helper scripts for both macOS/Linux (bash) and Windows (PowerShell) to detect and run supported toolchains.

Code Change Verification

Name: Code Change Verification
Author: future3OOO

byfuture3OOO

•

Security & Testing

Enforces a mandatory verification checklist including linting, type-checking, and testing to prevent regressions before completing tasks.

The Code Change Verification skill ensures that Claude agents maintain high code quality by running a repository's full verification stack—including formatting, linting, type-checking, and test suites—before marking any code change as complete. It provides a standardized framework for reducing regressions in runtime code, build configurations, and CI scripts, while offering intelligent heuristics for handling complex logic changes. This skill is essential for maintaining project integrity and ensuring that automated changes meet production standards by requiring agents to validate their work against local runbooks and standard toolchains.

Key Features

01Cross-platform support with helper scripts for macOS, Linux, and Windows

02Automated verification stack execution (format, lint, type-check, test)

03Heuristic-based testing for parser, selector, and routing logic

04Smart skip logic for documentation and comment-only changes

051 GitHub stars

06Regression prevention for auth, billing, and build tooling

Use Cases

01Validating runtime code changes before finalizing a pull request

02Ensuring CI/CD and build configuration updates don't break the pipeline

03Verifying complex logic changes with edge-case input testing

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add future3ooo/agentic-cockpit code-change-verification

For use in Claude.ai and ChatGPT

Key Features

01Cross-platform support with helper scripts for macOS, Linux, and Windows

02Automated verification stack execution (format, lint, type-check, test)

03Heuristic-based testing for parser, selector, and routing logic

04Smart skip logic for documentation and comment-only changes

051 GitHub stars

06Regression prevention for auth, billing, and build tooling

Use Cases

01Validating runtime code changes before finalizing a pull request

02Ensuring CI/CD and build configuration updates don't break the pipeline

03Verifying complex logic changes with edge-case input testing

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add future3ooo/agentic-cockpit code-change-verification

For use in Claude.ai and ChatGPT