generated from john/python-template
This commit is contained in:
@@ -9,7 +9,7 @@ agent: Python Architect Reviewer
|
||||
Execute a comprehensive, evidence-based code review of the target codebase.
|
||||
|
||||
## Target Scope
|
||||
- **Review Target:** ${{input:target_path:./}}
|
||||
- **Review Target:** the repository root, unless the invoker names a narrower path; review that path instead.
|
||||
- **Source Root:** `src/`
|
||||
- **Docs Root:** `docs/`
|
||||
- **Focus Areas:** FastAPI endpoints, NiceGUI components, SQLModel persistence, asyncio workers, Pydantic V2 models, and OpenRouter provider adapters.
|
||||
@@ -17,7 +17,7 @@ Execute a comprehensive, evidence-based code review of the target codebase.
|
||||
## Execution Rules
|
||||
1. Map repository layout, dependency manifests, and configuration files from the project root before inspecting modules.
|
||||
2. Read real code modules under `src/` (or the specified target path); cite exact file paths and line ranges for every finding.
|
||||
3. Validate issues using terminal tools (`ruff check`, `pytest`, `ty`) where appropriate.
|
||||
3. Validate issues by running `uv run ruff check .`, `uv run ty check`, and `uv run pytest -q -m "not external"`. Nothing is on `PATH` in this `uv` project, so bare `ruff`/`ty`/`pytest` will fail.
|
||||
4. Check for duplication, divergent implementations, and extractable helpers.
|
||||
5. Format the entire review following the standardized 6-section template defined in the `python-code-reviewer` skill.
|
||||
6. Write the final report as a Markdown file to `./docs/code-review-${{current_date}}.md`.
|
||||
5. Format the entire review following the standardized 10-section template defined in the `python-code-reviewer` skill.
|
||||
6. Write the final report to `./docs/reviews/<YYYY-MM-DD>-code-review.md`, using today's date. This path is defined by the skill; do not write the report anywhere else.
|
||||
Reference in New Issue
Block a user