code-change-verification

Automates formatting, linting, type checking, and tests for Python Make workflows.

Updated Dec 6, 2016

Search Tags:#python #make #lint #format #ci #tests #code-verification

Ready to run

npx skills add https://github.com/majunbao/learn --skill code-change-verification-majunbao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-change-verification
Source: https://github.com/majunbao/learn/tree/main/openai-agents-python_tags/openai-agents-python-0.14.6/.agents/skills/code-change-verification
Command: npx skills add https://github.com/majunbao/learn --skill code-change-verification-majunbao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, make, and includes scripts (resource) components.

What problem does it solve?

Ensure changes that affect runtime code, tests, or build/test behavior are validated by formatting, linting, type checking, and tests passing.

Core Features & Use Cases

Automatic formatting: Run formatting to enforce consistent code style.
Quality verification: Linting, type checking, and tests run to catch issues early.
Use Case: When you modify core library code or test configuration, use this skill to verify the entire verification stack before merging.

Quick Start

From the repository root, run the verification script to execute formatting, linting, type checking, 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 formatting, linting, and tests before merging Python code changes?▼

To run formatting, linting, type checking, and tests for Python code changes, execute the verification script from the repository root. This automates the full code quality verification stack to validate runtime code modifications before merging.

What is a Make-based workflow for Python code verification?▼

A Make-based workflow for Python code verification uses Makefile targets like make format, make lint, make typecheck, and make tests to enforce code quality. It automates formatting, linting, type checking, and test execution for code changes.

Do I need git and make to automate Python code quality checks?▼

Yes, you need git and make installed to automate Python code quality checks using this verification stack. The skill relies on Make-based workflows to execute targets for formatting, linting, type checking, and tests.

When should I run the full code quality verification stack for Python repositories?▼

You should run the full code quality verification stack when you modify core library code, tests, or build configurations. This ensures runtime code changes and test behavior are validated by formatting, linting, type checking, and passing tests.

Can I use this verification stack for non-Makefile Python projects?▼

No, this verification stack requires a Make-based workflow with specific targets. It applies to Python repositories that have make format, make lint, make typecheck, and make tests configured to enforce code quality.