What problem does it solve? Python contributors to the MindIE-SD repository face confusing lint behavior: the CI gate reads pre-commit/pyproject.toml (line-length 120, minimal ruff rule set) while local IDEs read the root pyproject.toml (line-length 100, broader rules), causing "local fails but CI passes" confusion and accidental mass-reformatting of untouched code. ## Core Features & Use Cases - Gate Configuration Truth Source: Documents exactly which config file the pre-commit gate reads, with a diff table of divergent values (line-length, quote-style, enabled rule sets) between the two pyproject.toml files. - Hook Inventory & Rule Classification: Lists all 21 pre-commit hook entries (ruff, pylint, bandit, codespell, typos, clang-format, clang-tidy, gitleaks, markdownlint) and classifies each style rule as gate-enforced, review convention, or unverifiable historical record. - Anti-Diff-Pollution Rules: Forbids formatting unmodified lines, renaming existing variables, or changing quote styles, keeping MRs reviewable. - Use Case: A developer sees E501 Line too long (102 > 100) locally but CI passes; this Skill explains the gate uses 120 columns with E501 disabled, and provides the exact ruff check --config pre-commit/pyproject.toml commands to reproduce CI behavior. ## Quick Start Ask the AI to check and fix lint issues in your modified MindIE-SD Python file using the gate configuration before committing.
