a7b15298e0
Brings 47 local-only files from backup-local-main into the merge-upstream
branch at their pre-rename paths. Subsequent steps will rename these to
the ce-* convention and port shared-file merges.
Includes:
- Custom skills: john-voice, jira-ticket-writer, hugo-blog-publisher,
weekly-shipped, proof-push, ship-it, story-lens, sync-confluence,
excalidraw-png-export, python-package-writer, fastapi-style,
upstream-merge
- Custom agents: design-conformance-reviewer, tiangolo-fastapi-reviewer,
zip-agent-validator, python-package-readme-writer, lint
- Custom commands: essay-edit, essay-outline, pr-comments-to-todos,
resolve_todo_parallel, workflows/{plan,review,work}
- Local mods to ce-review/SKILL.md + review-output-template.md (will be
ported to ce-code-review in a later step)
Co-Authored-By: Claude Opus 4.7 (1M context) <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 its own linters configured by looking for a pre-commit config file
|
|
3. **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
|
|
4. **Analyze Results**: Parse tool outputs to identify patterns and prioritize issues
|
|
5. **Take Action**: Commit fixes with `style: linting`
|