pyright-delta

Detect new pyright errors introduced by pull requests in modified files.

1.4k|208|Updated May 31, 2015
One-click install
npx skills add https://github.com/aio-libs/aiobotocore --skill pyright-delta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pyright-delta
Source: https://github.com/aio-libs/aiobotocore/tree/main/plugins/aiobotocore-bot/skills/pyright-delta
Command: npx skills add https://github.com/aio-libs/aiobotocore --skill pyright-delta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps to identify new pyright errors introduced by pull requests in the files they modify, ensuring code quality is maintained.

Core Features & Use Cases

  • Error Detection: Detects new pyright errors introduced by changes in the codebase.
  • Baseline Comparison: Compares the current code with a baseline to find new errors.
  • File Restriction: Only reports errors in files that have been modified by the pull request.
  • Use Case: Ideal for developers and code reviewers who want to ensure that pull requests do not introduce new pyright errors.

Quick Start

Run the pyright-delta skill to check for new pyright errors in the current pull request.

Frequently Asked Questions about pyright-delta

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

FAQPage Schema
How do I check for new pyright errors introduced by a pull request?

To check for new pyright errors introduced by a pull request, run a delta analysis that compares current code against a baseline. This process restricts reporting to modified files, ensuring only newly introduced errors are highlighted.

What is pyright delta analysis and how does it work?

Pyright delta analysis identifies new type checking errors in modified files by comparing the current codebase state against a baseline. It works by restricting the error report to only files touched by the pull request, maintaining code quality.

Do I need git and pyright installed to detect new errors in touched files?

Yes, you need both git and pyright installed to detect new errors in touched files. Git identifies the modified files in the pull request, while pyright performs the static type checking required to generate the delta report.

Can I restrict pyright error detection to only modified files in a code review?

Yes, you can restrict pyright error detection to only modified files during a code review. This baseline comparison approach ensures reviewers only see new errors introduced by the pull request, ignoring pre-existing issues.

How do I generate a baseline comparison for pyright errors in a PR?

To generate a baseline comparison for pyright errors in a PR, run a delta analysis script that executes pyright on both the base and modified code. This outputs a report isolating new errors specifically within the touched files.

What's the best way to ensure code quality by detecting new type errors in modified files?

The best way to ensure code quality by detecting new type errors in modified files is running a delta analysis. This compares the pull request changes against a pyright baseline, preventing the introduction of new errors while avoiding noise from pre-existing issues.