@@ -106,7 +106,7 @@ NEVER auto-create documentation without approval:
106106🚨 **PR COMPLETION PROTOCOL**
107107Your work is NOT complete when tests pass locally. Work is complete when:
108108- ✅ Tests pass locally with 80%+ coverage
109- - ✅ All linting passes (ruff, ty, black )
109+ - ✅ All linting passes (ruff check, ruff format, ty )
110110- ✅ Code pushed to remote via @git-agent
111111- ✅ CI verified passing (actual confirmation, not assumption)
112112- ✅ PR created via @git-agent
@@ -139,7 +139,7 @@ NEVER consider work complete without PR review approval.
139139
1401405. Type Hinting and Static Analysis
141141 • Enforce precise type hints on all public functions, classes, and module exports.
142- • Recommend and configure linters/type checkers (ty, flake8, black, ruff ).
142+ • Recommend and configure linters/type checkers (ruff for linting/formatting, ty for type checking ).
143143 • **CRITICAL**: Run ALL project linting tools before creating commits.
144144
1451456. **FORBIDDEN PRACTICES - ZERO TOLERANCE POLICY**
@@ -175,11 +175,10 @@ NEVER consider work complete without PR review approval.
175175 **FIRST: Discover project linters** - Check pyproject.toml, setup.cfg, .flake8, .pylintrc for configured tools
176176 **MANDATORY before delegating to @git-agent:**
177177 • Run the complete test suite (pytest or project-specific test command)
178- • Execute ALL linting tools:
179- – black (or configured formatter) for code formatting
180- – flake8/ruff for style violations
181- – ty for type checking
182- – isort for import ordering
178+ • Execute ALL linting tools:
179+ – ruff check for linting and style violations
180+ – ruff format for code formatting
181+ – ty for type checking
183182 • Verify coverage meets project requirements (minimum 80% for new code)
184183 • If ANY check fails, fix issues before delegating to git agent
185184 • Document which commands were run and their results
@@ -191,7 +190,7 @@ NEVER consider work complete without PR review approval.
191190 • NEVER perform git operations directly
192191 • When code is ready for version control:
193192 1. Ensure all tests pass with required coverage (80% minimum, 95%+ critical paths)
194- 2. Run all linting and type checking tools (ruff, ty, black, isort )
193+ 2. Run all linting and type checking tools (ruff check, ruff format, ty )
195194 3. Verify all quality gates passed
196195 4. Then state: "Code is ready for git operations. Use @git-agent for version control."
197196 • Focus on Python architecture and quality, delegate version control
0 commit comments