pyrefly-type-coverage

Configure pyrefly.toml and run Pyrefly checks to identify type coverage gaps.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/steleman/pytorch-cuda-2.11.0 --skill pyrefly-type-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pyrefly-type-coverage
Source: https://github.com/steleman/pytorch-cuda-2.11.0/tree/main/.claude/skills/pyrefly-type-coverage
Command: npx skills add https://github.com/steleman/pytorch-cuda-2.11.0 --skill pyrefly-type-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pyrefly-type-coverage helps teams improve Python type safety by guiding removal of blanket suppression and adding precise type annotations through Pyrefly configurations and checks.

Core Features & Use Cases

  • Remove suppression directives like pyre-ignore-all-errors to enable type checking.
  • Add per-file or per-directory sub-configs to pyrefly.toml to enforce stricter type checks.
  • Run Pyrefly checks to surface missing annotations and progressively annotate code.
  • Use in projects aiming for robust type safety across large codebases.

Quick Start

Remove existing suppression comments, configure pyrefly.toml, and run pyrefly check on your target file.

Frequently Asked Questions about pyrefly-type-coverage

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

FAQPage Schema
How do I remove pyre-ignore-all-errors and enforce stricter Python type checking?

Remove blanket suppression directives like pyre-ignore-all-errors and configure pyrefly.toml with per-file or per-directory settings to enforce stricter Python type checking across your project.

How do I configure pyrefly.toml for per-directory type checking strictness?

Configure pyrefly.toml for per-directory type checking by adding sub-configs that target specific modules, enabling progressively stricter type checks and surfacing missing annotations in your Python codebase.

What is the best way to improve Python type coverage in a large codebase?

Improve Python type coverage in a large codebase by running Pyrefly checks to surface missing annotations, then applying per-file configurations in pyrefly.toml to enforce explicit typing project-wide.

Can I use Pyrefly to progressively add type annotations to existing Python files?

Yes, you can use Pyrefly to progressively add type annotations by running targeted checks on specific files or directories, identifying coverage gaps, and applying explicit annotations to resolve them.

Why does removing blanket suppression directives break my Pyrefly checks?

Removing blanket suppression directives like pyre-ignore-all-errors surfaces previously hidden type errors, requiring you to add explicit Python type annotations or per-file exceptions in pyrefly.toml to resolve them.