Clarify Python Verification Commands - #813
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the fleet’s Python codestyle Skill text to explicitly trigger when selecting/running Python verification commands and to route agents to repository-specific guidance (via OPERATIONS.md) before assuming generic pytest-based workflows. This keeps verification instructions aligned with the repo’s lint-only unittest profile and the generated skill distributions.
Changes:
- Expand the
python-codestyleSkill description to cover choosing/running Python format/lint/type-check/test commands (not just authoring Python code/tests). - Clarify the “Two profiles” section to consult
OPERATIONS.mdbefore selecting tooling/tests, and to discourage pytest in lint-only repos. - Regenerate the distributed skill copies and update the Claude plugin source digest.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| .github/skills/python-codestyle/SKILL.md | Updates canonical fleet skill guidance for Python verification command selection. |
| .agents/skills/python-codestyle/SKILL.md | Regenerates the agent-skill distribution copy to match the canonical skill text. |
| .claude-plugin/fleet-skills/skills/python-codestyle/SKILL.md | Regenerates the Claude plugin skill copy to match the canonical skill text. |
| .claude-plugin/fleet-skills/.source-digest | Updates the plugin distribution digest for the regenerated skill set. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
Why
The previous trigger covered Python edits and pytest authoring, but not running tests. That gap allowed a generic pytest invocation in this lint-only repository and produced a false missing-dependency diagnosis.
Verification
uvx coverage@latest run --source=scripts,spec,host-setup -m unittest discover -s scripts/tests(727 tests passed)python3 scripts/tests/test_build_dist.py(25 tests passed)python3 scripts/build_dist.py --check