pyhd

Format and lint Python files with ruff while verifying external APIs.

13|3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danicat/skills --skill pyhd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pyhd
Source: https://github.com/danicat/skills/tree/main/pyhd
Command: npx skills add https://github.com/danicat/skills --skill pyhd

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes uncertainty and inconsistency in Python codebases by enforcing an immediate ruff-based format and lint workflow after every change, so style issues never linger.

Core Features & Use Cases

  • Ruff formatting and auto-fixing: Immediately runs ruff check --fix and ruff format for the modified file to keep changes clean and compliant.
  • API correctness guardrails: Requires verifying external package APIs via web documentation, inspecting installed packages, or using help() before relying on library behavior.
  • Quality standards guidance: Points to a dedicated best_practices reference covering PEP 8, type hinting, imports, error handling, and testing expectations.

Quick Start

Use the pyhd skill when editing any Python file in a project, then run ruff check --fix and ruff format on that file immediately after each modification.

Frequently Asked Questions about pyhd

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

FAQPage Schema
How do I automate Python code formatting and linting with ruff?

Automate Python code formatting and linting by running uv ruff check --fix and uv ruff format on each modified file immediately after editing to ensure changes remain clean and compliant.

What should I do when ruff reports non-auto-fixable linting errors?

When ruff reports non-auto-fixable linting errors, you must manually resolve them in the Python code before proceeding, as the automated check --fix command only handles correctable style violations.

How do I ensure correct external package API usage when refactoring Python modules?

Ensure correct external package API usage by verifying behavior through web documentation, inspecting installed packages, or using the help() function before relying on library implementations in your Python code.

Does this ruff workflow include guidance on Python type hints and testing expectations?

Yes, the ruff workflow includes a best practices reference covering PEP 8, type hinting, imports, error handling, and testing expectations to enforce consistent quality standards across Python modules.

What is the best way to maintain style consistency when maintaining Python codebases?

The best way to maintain style consistency is enforcing an immediate ruff-based format and lint workflow after every change, ensuring style issues never linger during module editing and refactoring.