typing-exclusion-worker

The project keeps a list of files that are let off Python's type checks; this takes a few assigned files off that list, fixes the errors that surface, and reports back to whoever is running the batch.

WHEN TO USE

SCOPE

USE FOR

Take one assigned code module off the project's type-checking exclusion list and fix the errors it exposes.
Work through a scoped typing-debt batch as one of several parallel workers reporting to a manager.
Produce a structured batch summary of modules fixed, files changed, and validation results.

NOT FOR

Does not expand fixes into other teams' modules without the manager's approval.
Does not use blanket type-ignore comments, only narrow reason-tagged ones when unavoidable.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (8)

Typing Exclusion Worker

Purpose

Execute one assigned typing batch safely and predictably:

remove only assigned modules from mypy exclusions,
fix surfaced typing issues in scope,
run required checks,
return a consistent summary for the manager/orchestrator.

Inputs Required

Before starting, confirm these inputs exist in the task prompt:

worktree/branch name,
exact module list to remove from exclusion,
ownership/domain boundary,
expected validation commands (if customized).

If any are missing, ask for them before editing.

Scope Rules (Hard Constraints)

Only remove assigned module entries from the mypy exclusion list in pyproject.toml.
Keep code changes in assigned scope unless a direct dependency is required to pass typing/tests.
Do not expand to cross-team modules unless explicitly approved by the manager.
Avoid blanket # type: ignore; if unavoidable, use narrow ignore[code] with a short reason.

Execution Workflow

Apply exclusion change
- Remove assigned modules from the exclusion override in pyproject.toml.
Run mypy on assigned scope
- Prefer targeted paths first for fast feedback.
- Fix errors using explicit typing patterns (isinstance narrowing, accurate return types, typed class attrs, relation-safe model access).
Run tests for touched area
- Execute targeted pytest for modified modules/tests.
- Fix regressions before continuing.
Run pre-commit on changed files
- Run pre-commit run --files <changed files>.
- If hooks auto-fix files, rerun until clean.
Final verification
- Re-run targeted mypy and tests after final edits.
- Ensure no unrelated files were changed.

Python Typing Best Practices

Prefer precise types over Any.
Use type narrowing on unions before attribute access.
Keep method overrides signature-compatible with base classes.
Annotate class attributes in tests/helpers when inference is weak.
Use relation objects (obj.related) when stubs do not expose raw *_id attributes.

Required Output Template

Return this exact structure at the end of each batch:

## Batch Summary

- Branch/worktree: `<name>`
- Ownership/domain: `<team-or-domain>`

### Modules Removed From Exclusion

- `<module.path.one>`
- `<module.path.two>`

### Files Changed

- `<path>`
- `<path>`

### Key Typing Fixes

- `<short rationale + fix>`
- `<short rationale + fix>`

### Validation

- `mypy`: `<pass/fail + scope>`
- `pre-commit --files`: `<pass/fail>`
- `pytest`: `<pass/fail + scope>`

### Notes

- Remaining blockers: `<none or details>`
- Any new ignore entries: `<none or file + ignore code + reason>`

Stop Conditions (Escalate to Manager)

Stop and report instead of widening scope when:

fixes require touching another team/domain,
exclusion conflicts in pyproject.toml cannot be resolved safely,
error volume indicates batch is too large and should be split.

Local tool required

1 FOR YOU

01
Have mypy, pytest and pre-commit set up in the repo
Work inside a Python codebase that has mypy, pytest and pre-commit installed and configured, with a pyproject.toml mypy exclusion list to trim, since the skill runs all three to remove and verify each assigned module.

Listed as free: Connected services may require an account or charge fees.
Installation: One command — usually under 2 minutes.

This skill ships inside the Sentry Engineering Skills plugin. Listed package contents include 2 agents. Installed components and skill versions may vary by AI tool.

Install just this skill

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add getsentry/skills --skill "typing-exclusion-worker" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

Install the whole plugin

This route installs the Sentry Engineering Skills plugin package selected for your AI tool.

Claude Code

Add Sentry's marketplace, then install the plugin

Run both lines in a terminal. The first adds Sentry's marketplace, which is this repository; the second installs the sentry-skills plugin, which Sentry describes as agent skills for its employees, plus two subagents. It installs for you in every project; restart Claude Code afterwards, as Sentry's README says.

01

claude plugin marketplace add getsentry/skills

02

claude plugin install sentry-skills@sentry-skills

Open plugin page ↗

What's inside

Files included with this skill.

View on GitHub

The repository is licensed under Apache-2.0 — use, modification, and redistribution are allowed under that license’s terms.

View the repository’s license file on GitHub →

Typing Exclusion Worker

Purpose

Inputs Required

Scope Rules (Hard Constraints)

Execution Workflow

Python Typing Best Practices

Required Output Template

Stop Conditions (Escalate to Manager)

Local tool required

Install just this skill

Install the whole plugin

Add Sentry's marketplace, then install the plugin

What's inside

More skills

agents-md

blog-writing-guide

brand-guidelines

claude-settings-audit

code-review

code-simplifier