// This skill helps lint Python code using ruff. Use when the user asks to "lint", "check code quality", or "fix style issues".
This skill should be used when the user asks to "trigger an eval", "run evaluation", "run swebench", "run gaia", "run benchmark", "compare eval runs", "compare evaluation results", "check eval regression", "compare benchmark results", "what changed in the eval", "diff eval runs", or mentions triggering, comparing, or reporting on SWE-bench, GAIA, or other benchmark evaluation results. Provides workflow for triggering evaluations on different benchmarks, finding and comparing runs, and reporting performance differences.
This skill should be used when the user asks to "release the SDK", "prepare a release", "publish a new version", "cut a release", "do a release", or mentions the SDK release checklist or release process. Guides through the full software-agent-sdk release workflow from version bump to PyPI publication, emphasizing human checkpoints.
This skill should be used when the user asks to "test a saas cross-repo feature", "deploy a feature branch to staging", "test SDK against OH Cloud branch", "e2e test a cloud workspace feature", "test secrets saas inheritance", or when changes span the SDK and OpenHands enterprise and need end-to-end validation against a staging deployment.
This skill should be used when the user asks to "rollout a feature", "complete feature release", "propagate SDK feature", "track feature support", "what's missing for feature X", or mentions checking CLI/GUI/docs/blog support for SDK features. Guides agents through the multi-repository feature release workflow from SDK to docs to marketing.
Guide for debugging failing example tests in the `test-examples` labeled workflow. Use this skill when investigating CI failures in the run-examples.yml workflow, when example scripts fail to run correctly, when needing to isolate specific test failures, or when analyzing workflow logs and failure patterns.
Project coding standards and style guidelines. Always follow these conventions when writing or reviewing code.
| name | python-linting |
| description | This skill helps lint Python code using ruff. Use when the user asks to "lint", "check code quality", or "fix style issues". |
| license | MIT |
| compatibility | Requires Python and ruff |
| metadata | {"author":"openhands","version":"1.0"} |
| triggers | ["lint","linting","code quality","style check","ruff"] |
This skill provides instructions for linting Python code using ruff.
Run ruff to check for issues:
ruff check .
To automatically fix issues:
ruff check --fix .
--select E,W - Only check for errors and warnings--ignore E501 - Ignore line length errors--fix - Automatically fix fixable issuesexample.py:1:1: F401 [*] `os` imported but unused
example.py:5:5: E302 Expected 2 blank lines, found 1
Found 2 errors (1 fixable).