Code Change Verification

Name: Code Change Verification
Author: yasik

ASecurity

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

9 stars
0 votes
0 copies
3 views
Added September 3, 2026

ai-agentspythonbash

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 3, 2026

npx -y skills add yasik/agentlane --skill code-change-verification --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Change Verification?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Change Verification

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yasik-code-change-verification/badge)](https://www.skillsdirectory.com/skills/yasik-code-change-verification)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

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

# Code Change Verification

## Overview

Ensure work is only marked complete after formatting, linting, type checking, and tests pass. Use this skill when changes affect runtime code, tests, or build/test configuration. You can skip it for docs-only or repository metadata unless a user asks for the full stack.

## Quick start

1. macOS/Linux: `bash .agents/skills/code-change-verification/scripts/run.sh`.
2. If any command fails, fix the issue, rerun the script, and report the failing output.
3. Confirm completion only when all commands succeed with no remaining issues.

## Manual workflow

- If dependencies are not installed or have changed, run `make sync` first to install dev requirements via `uv`.
- Run from the repository root in this order: `make format`, `make lint`, `make typecheck`, `make tests`.
- Do not skip steps; stop and fix issues immediately when a command fails.
- Re-run the full stack after applying fixes so the commands execute in the required order.

## Resources

### scripts/run.sh

- Executes the full verification sequence with fail-fast semantics from the repository root. Prefer this entry point to ensure the required commands run in the correct order.