verify

Run Black, isort, Flake8, and pytest checks on Python projects.

Updated May 29, 2025

Search Tags:#pytest #code-quality #black #ci-cd #lint #format #flake8

Ready to run

npx skills add https://github.com/Lincyaw/paperops --skill verify-lincyaw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/Lincyaw/paperops/tree/main/.claude/skills/verify
Command: npx skills add https://github.com/Lincyaw/paperops --skill verify-lincyaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates code quality checks to ensure the project's codebase adheres to formatting, style, and reliability standards before commits.

Core Features & Use Cases

Format consistency: Run Black to enforce consistent formatting across the codebase.
Import order and linting: Run isort and Flake8 to ensure clean imports and style compliance.
Test readiness: Execute pytest to validate that changes do not break existing behavior.
Use Case: Before pushing a feature branch, run all checks to catch issues early.

Quick Start

Run the verify skill against your repository to perform formatting, import sorting, linting, and tests.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I automate Python code formatting and linting before commits?▼

Automating Python code formatting and linting before commits involves running Black for formatting, isort for import sorting, and Flake8 for style checks to enforce consistency and catch issues early.

What is the best way to run pytest and lint checks together for a Python project?▼

The best way to run pytest and lint checks together is executing a unified verification workflow that runs Black, isort, Flake8, and pytest sequentially to validate code style and test readiness.

Can I use Black and Flake8 in a CI workflow to catch code quality issues?▼

Yes, you can use Black and Flake8 in a CI workflow to catch code quality issues. Applying these automated checks in development and CI pipelines enforces standards before commits and merges.

Does automated code verification with Black, isort, and Flake8 fix import order and style errors?▼

Automated code verification with Black, isort, and Flake8 fixes import order and style errors. Black enforces formatting consistency, isort cleans imports, and Flake8 reports remaining style compliance issues.

Why does my Python project need both formatting and test execution before merging?▼

Your Python project needs both formatting and test execution before merging to guarantee codebase quality. Formatting enforces style standards while pytest execution validates that changes do not break existing behavior.

What are the limitations of relying only on Flake8 for Python code quality checks?▼

Relying only on Flake8 for Python code quality checks limits automated formatting and import sorting. Flake8 reports style issues but does not automatically format code like Black or sort imports like isort.