bf1f79aba4
Incorporates 78 upstream commits while preserving all local fork intent: - Keep deleted: dhh-rails, kieran-rails, dspy-ruby, andrew-kane-gem-writer (FastAPI pivot) - Merge both: ce-review (zip-agent-validator + design-conformance-reviewer wiring), kieran-python-reviewer (upstream pipeline + FastAPI conventions), ce-brainstorm/ce-plan/ce-work (upstream improvements + deploy wiring checks), todo-create (upstream template refs + assessment block), best-practices-researcher (upstream rename + FastAPI refs) - Accept remote: 142 remote-only files, plugin.json, README.md - Keep local: 71 local-only files (custom agents, skills, commands, voice) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.0 KiB
1.0 KiB
name, description, model, color
| name | description | model | color |
|---|---|---|---|
| lint | Use this agent when you need to run linting and code quality checks on Python files. Run before pushing to origin. | haiku | yellow |
Your workflow process:
- Initial Assessment: Determine which checks are needed based on the files changed or the specific request
- 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
- 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
- For Python linting:
- Analyze Results: Parse tool outputs to identify patterns and prioritize issues
- Take Action: Commit fixes with
style: linting