skills.rest
Dino-Stark
Dino-StarkCOMMUNITY
Explore all skills by this author →
GitHub

code-change-verification

Run formatting, linting, type checking, and tests with fail-fast semantics.

Updated Feb 15, 2026
Search Tags:#code quality#automation#testing#linting#verification#ci
One-click install
npx skills add https://github.com/Dino-Stark/generic-agent-core --skill code-change-verification-dino-stark
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-change-verification
Source: https://github.com/Dino-Stark/generic-agent-core/tree/main/references/openai-agents-python-main/.agents/skills/code-change-verification
Command: npx skills add https://github.com/Dino-Stark/generic-agent-core --skill code-change-verification-dino-stark

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that all code changes affecting runtime, tests, or build processes adhere to quality standards by automating formatting, linting, type checking, and testing.

Core Features & Use Cases

  • Automated Quality Checks: Runs essential verification steps to catch issues early.
  • Fail-Fast Execution: Stops immediately upon encountering any error, preventing further issues.
  • Use Case: Before merging a pull request that modifies core application logic, use this skill to guarantee that the code is well-formatted, lint-free, type-correct, and passes all unit tests.

Quick Start

Run the bash script located at .agents/skills/code-change-verification/scripts/run.sh from the repository root.

Frequently Asked Questions about code-change-verification

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

FAQPage Schema
How do I automate code formatting and linting before a pull request?▼

Automated code formatting and linting before a pull request is handled by executing a mandatory verification stack. This stack runs make targets for formatting, linting, type checking, and testing to ensure code quality standards are met.

What is a fail-fast verification process for runtime code changes?▼

A fail-fast verification process for runtime code changes stops execution immediately upon encountering any formatting, linting, type checking, or testing error. This prevents further issues and ensures only valid code passes the verification stack.

Does automated type checking and testing require specific make targets to run?▼

Yes, automated type checking and testing requires specific make targets for format, lint, mypy, and tests to be available. The verification stack depends on these targets to execute checks within the Python repository environment.

How do I run automated quality checks for Python repository modifications?▼

To run automated quality checks for Python repository modifications, execute the bash script located at .agents/skills/code-change-verification/scripts/run.sh from the repository root. This triggers the mandatory verification stack for runtime, test, or build changes.

Why does my code verification stop immediately when encountering an error?▼

Code verification stops immediately when encountering an error due to fail-fast execution semantics. This design halts the formatting, linting, mypy, and testing stack instantly to surface issues early and prevent cascading build failures.

Related Skills

Explore More Software Engineering Skills→
zaziedlmzaziedlm

code-change-verification

Run formatting, linting, type checking, and tests in sequence.

Community
Intermediate
WanxiaJaneYangWanxiaJaneYang

repo-standards

Validate code formatting, linting, type-checking, and tests for pull requests.

Community
Basic
leboncoinleboncoin
92

run-quality-checks

Run linting, type checking, formatting, and tests for Spark UI projects.

Official
Intermediate
PenHsuanWangPenHsuanWang

db-explorer-architect

Develop a full-stack DB Explorer with FastAPI, React, and hexagonal architecture.

Community
Advanced