메뉴
Python 差分を pyright、pytest、ruff、型境界、API 挙動、OOP 可読性根拠で厳密に確認する。
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | python-review |
| description | Python 差分を pyright、pytest、ruff、型境界、API 挙動、OOP 可読性根拠で厳密に確認する。 |
Use the command packet before applying this skill's workflow:
python3 tools/agent_tools/skill_tool_commands.py show --skill python-review --format text
Execute the required and task-matching conditional commands that the packet prints.
agents/skills/python-review.md を読みます。pyright を実行または確認します。pytest tests/ を実行または確認します。ruff check python tests --select D,E,F,I,UP --ignore E501 を実行または確認します。python3 tools/agent_tools/check_convention_compliance.py を実行または確認し、
定義順契約が review evidence に見えていることを確認します。Protocol、継承、公開 API、型境界、依存方向を持つ場合は、$oop-readability-check / python3 tools/oop/python/readability.py を下流根拠として実行または確認し、SOLID 原則シグナル数を確認します。
レポート内の Single responsibility、Open/closed、Liskov substitution、
Interface segregation、Dependency inversion のシグナルを review evidence として使います。python3 tools/agent_tools/check_solid_evidence.py --root . <changed-python-paths> --evidence <oop-readability-report> を実行または確認し、レポートの scanned_paths が確認対象の SOLID 対象ファイルを覆っていることを確認します。Use when agent-side working philosophy, interaction lessons, task retrospectives, repeated routing misses, missed skill invocation, or recurrence-prevention feedback should be logged without mixing them into user preferences.
Use when exploring, refactoring, or choosing an algorithm under proof obligations; builds JIT-canonical IR, lemma dependency graphs, algorithmic blocker frontiers, and algorithm-change guidance before handing terminal proof work to formal-proof-workflow.
Use when designing, implementing, reviewing, or diagnosing numerical optimization, solvers, preconditioners, convergence, gradients, Jacobians, Hessians, KKT conditions, tolerances, or optimization benchmarks; fixes the mathematical and validation contract before code or experiment changes.
Use when a change needs oracle/spec-risk classification or resilient, adversarial static test design, including behavior contracts, oracle choice, property/metamorphic candidates, mutation adequacy, or brittle-test diagnosis.
Use when updating AgentCanon itself, refreshing a vendored vendor/agent-canon submodule pin, repairing AgentCanon root runtime views, applying AgentCanon update TODOs, or routing local AgentCanon source commits through a proper AgentCanon branch and PR before parent pin updates.
Use when accumulated AgentCanon eval evidence is missing, stale, or failing; runs registered eval producers, validates eval family accumulation, and stores evidence through the log archive instead of hand-writing reports.