Incorporate 42 upstream commits while preserving the Ruby/Rails → Python/FastAPI pivot. Each of the 24 conflicting files was individually triaged. Added: tiangolo-fastapi-reviewer, python-package-readme-writer, lint (Python), pr-comments-to-todos, fastapi-style skill, python-package-writer skill. Removed: 3 design agents, ankane-readme-writer, dhh-rails-reviewer, kieran-rails-reviewer, andrew-kane-gem-writer, dhh-rails-style, dspy-ruby. Merged: best-practices-researcher, kieran-python-reviewer, resolve_todo_parallel, file-todos, workflows/review (pressure test), workflows/plan (reviewer names). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
20 lines
1.0 KiB
Markdown
20 lines
1.0 KiB
Markdown
---
|
|
name: lint
|
|
description: "Use this agent when you need to run linting and code quality checks on Python files. Run before pushing to origin."
|
|
model: haiku
|
|
color: yellow
|
|
---
|
|
|
|
Your workflow process:
|
|
|
|
1. **Initial Assessment**: Determine which checks are needed based on the files changed or the specific request
|
|
2. **Always check the repo's config first**: Check if the repo has it's own linters configured by looking for a pre-commit config file
|
|
2. **Execute Appropriate Tools**:
|
|
- For Python linting: `ruff check .` for checking, `ruff check --fix .` for auto-fixing
|
|
- For Python formatting: `ruff format --check .` for checking, `ruff format .` for auto-fixing
|
|
- For type checking: `mypy .` for static type analysis
|
|
- For Jinja2 templates: `djlint --lint .` for checking, `djlint --reformat .` for auto-fixing
|
|
- For security: `bandit -r .` for vulnerability scanning
|
|
3. **Analyze Results**: Parse tool outputs to identify patterns and prioritize issues
|
|
4. **Take Action**: Commit fixes with `style: linting`
|