code-change-verification

Name: code-change-verification
Availability: InStock
Author: sisyphus1212

Run format, lint, mypy, and tests for Python repository changes.

Updated Feb 23, 2026

Search Tags:#quality #mypy #lint #format #ci #tests #code-change

Ready to run

npx skills add https://github.com/sisyphus1212/codex-fusion-starter-template --skill code-change-verification-sisyphus1212

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-change-verification
Source: https://github.com/sisyphus1212/codex-fusion-starter-template/tree/main/scaffold/.agents/skills/code-change-verification
Command: npx skills add https://github.com/sisyphus1212/codex-fusion-starter-template --skill code-change-verification-sisyphus1212

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the OpenAI Agents Python repository.

Core Features & Use Cases

Enforces a consistent verification stack: format, lint, typing (mypy), and tests.
Applies to pull requests and commits that touch runtime code, tests, or CI/configuration to ensure baseline quality.
Use Case: before merging, run the verification to catch regressions and compile-time errors.

Quick Start

From the repository root, run the code-change-verification verification sequence to execute format, lint, mypy, and tests.

Frequently Asked Questions about code-change-verification

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

FAQPage Schema

How do I run format, lint, mypy, and tests before merging Python code changes?▼

Run format, lint, mypy, and tests by executing the verification sequence from the repository root. This stack validates formatting, linting, typing, and tests to catch regressions and compile-time errors before merging code changes.

When should I enforce the verification stack for Python runtime code changes?▼

Enforce the verification stack when changes impact runtime code, tests, or build and test behavior. It applies to pull requests and commits touching runtime code, tests, or CI configuration to ensure baseline quality.

What does the mandatory code change verification process include?▼

The mandatory code change verification process includes running format, lint, typing with mypy, and tests. It surfaces clear failure messages when any step fails, ensuring changes pass format, lint, and tests.

Do I need to configure CI to run the format, lint, mypy, and test verification?▼

No external CI configuration is required to run the verification locally. The sequence executes format, lint, mypy, and tests via provided scripts or targets directly from the repository root to validate code changes.

Why does my code change verification fail when running the sequence?▼

Code change verification fails when formatting, linting, mypy typing, or tests encounter errors. The sequence surfaces clear failure messages for any step that fails, highlighting the specific issue preventing validation.