v2-pyright-heal

Iteratively run Pyright and apply code fixes to resolve Python type errors.

Updated May 9, 2026
One-click install
npx skills add https://github.com/Ruclo/thesis-artifact --skill v2-pyright-heal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: v2-pyright-heal
Source: https://github.com/Ruclo/thesis-artifact/tree/main/v2/skills/v2-pyright-heal
Command: npx skills add https://github.com/Ruclo/thesis-artifact --skill v2-pyright-heal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uv, pyright.

What problem does it solve?

This Skill resolves persistent Python type errors and attribute mismatches by iteratively running the Pyright type checker and applying targeted code fixes to ensure codebase integrity.

Core Features & Use Cases

  • Iterative Healing: Automatically runs Pyright, parses error logs, and applies fixes until the code is clean or the iteration limit is reached.
  • Intelligent Patching: Handles common issues like missing imports, incorrect attribute access, type mismatches, and undefined variables without resorting to type-ignore comments.
  • Use Case: Use this tool to automatically resolve type-checking failures in complex test suites or utility modules after refactoring, ensuring all type annotations and imports are correct.

Quick Start

Run the v2-pyright-heal skill on the specified file path to automatically detect and fix all type-related errors.

Frequently Asked Questions about v2-pyright-heal

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

FAQPage Schema
How do I automatically fix Python type errors reported by Pyright?

You can automatically fix Python type errors by iteratively running Pyright and applying programmatic code edits to resolve missing imports, incorrect attributes, and type mismatches until the codebase passes strict type checking.

What is the best way to resolve type checking failures after refactoring a Python test suite?

The best way to resolve post-refactoring type checking failures is to use an automated iterative healing process that parses Pyright logs and patches type mismatches and undefined variables in-place without relying on type-ignore comments.

Do I need uv and pyright installed to automate Python type healing?

Yes, you need a functional environment with uv and pyright installed to perform automated type analysis and apply targeted in-place file modifications for strict type safety.

Can automated type fixing handle missing imports and incorrect attribute access in Python source files?

Automated type fixing intelligently handles missing imports, incorrect attribute access, type mismatches, and undefined variables in Python source files by applying targeted code patches instead of using type-ignore comments.

Does Pyright automated healing stop if the code still has type errors after multiple iterations?

The iterative healing process continuously runs Pyright and applies fixes until the code is completely clean or the predefined iteration limit is reached, ensuring semantic correctness without infinite loops.

Why should I avoid using type-ignore comments for persistent Python type mismatches?

Using type-ignore comments masks underlying semantic issues, whereas applying programmatic code edits resolves the actual type mismatches and attribute errors, maintaining strict type safety and codebase integrity.