Skip to content
Back to skills

2537 Linting Exceptions 1d62109e

ASecurity

Resolve linting errors — do not suppress them. Linting errors signal architectural issues, not noise.

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
developmentpythongosecurity

Works with

  • vscode

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 2537-linting-exceptions_1d62109e --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 2537 Linting Exceptions 1d62109e?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 2537 Linting Exceptions 1d62109e
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-2537-linting-exceptions-1d62109e/badge)](https://www.skillsdirectory.com/skills/tools-only-2537-linting-exceptions-1d62109e)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
paths:
  - "**/*.py"
  - "**/pyproject.toml"
---

# Linting Exception Conditions

Resolve linting errors — do not suppress them. Linting errors signal architectural issues, not noise.

## Acceptable Exceptions

Fix linting issues unless code falls into these categories:

1. **Vendored code** — third-party code copied without modification (not authored by model)
2. **What-not-to-do examples** — intentionally incorrect code for educational/negative test cases
3. **Historic Python version pinning** — code for Python <3.11 where modern syntax unavailable (currently no code in this category — verify before assuming)
4. **Python derivatives** — CircuitPython, MicroPython, or implementations with different syntax/missing stdlib modules

For these exceptions: update linting config files (`pyproject.toml`, `.vscode/settings.json`) to exclude the files. Do not use inline comments (`# noqa`, `# type: ignore`).

## Unacceptable Exceptions (MUST fix or escalate)

If NONE of the above apply:

1. Fix linting smell using `/hollistic-linting:hollistic-linting` Skill (exact methodology for addressing linting issues)
2. If unable to fix, document specific blocker
3. Adding `# type: ignore` or `# noqa` requires explicit user approval

## Rule Codes That MUST Always Be Fixed (never suppress)

- BLE001 (blind-except): Replace `except Exception` with specific exception types
- D103 (missing-docstring-in-public-function): Add docstrings to public functions
- TRY300 (try-consider-else): Restructure try/except/else blocks properly

## Per-File Exceptions in pyproject.toml (acceptable)

- `**/scripts/**`: T201 (print), S (security), DOC, ANN401, PLR0911, PLR0917, PLC0415
- `**/tests/**`: S, D, E501, ANN, DOC, PLC, SLF, PLR, EXE, N, T
- `**/assets/**`: PLC0415, DOC
- `typings/**`: N, ANN, A

**Touched Files Must Be Clean**: When files are modified/moved/renamed, all linting issues MUST be resolved before committing. Touching a file means taking responsibility for its quality.

SOURCE: User policy established in conversation (2025-01-15)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.