القائمة
Use when first opening an unfamiliar Python project. Quick analysis of project structure, dependencies, entry points, test setup, and tooling.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | project-onboard |
| description | Use when first opening an unfamiliar Python project. Quick analysis of project structure, dependencies, entry points, test setup, and tooling. |
pyproject.toml, setup.cfg, setup.py, requirements.txtuv.lock → uv, poetry.lock → poetry. If only requirements.txt exists, warn the user and suggest migrating to uv. Do NOT infer the manager from the presence of uv pip or pip — those are subcommands, not detection signals.pyproject.toml → [project] requires-pythonpyproject.toml → [project.scripts] or [tool.hatch.build.targets.wheel.scripts]src/ vs flat layouttests/, test/, or inline.env, conftest.py, alembic.ini, docker-compose.ymlruff: check [tool.ruff] in pyproject.toml or ruff.tomlbasedpyright: check [tool.basedpyright] or pyrightconfig.jsonpre-commit: check .pre-commit-config.yamlpytest: check [tool.pytest.ini_options][project.dependencies] and [project.optional-dependencies].venv/ exists, suggest uv sync (uv) or poetry sync (poetry) if notpython -c "import <main_pkg>" workspytest --co -q to list collected testsDepends() patterns existSummarize findings as:
Use when migrating a Python project from Poetry to uv. Covers running `uvx migrate-to-uv`, fixing pyproject.toml conversion gaps, rewriting Dockerfiles (poetry install -> uv sync), updating .gitlab-ci.yml, and verifying the result. Trigger keywords: migrate poetry to uv, migrate-to-uv, poetry -> uv, switch to uv, replace poetry.
Use when committing, creating PRs, or managing git history. Conventional commits, pre-commit hooks with ruff and basedpyright, branching conventions.
Use when working with poorly typed or legacy Python code. Covers gradual typing, safe annotation strategies, dynamic attributes, and monkeypatching without breaking behavior.
Use when refactoring Python code safely. Covers extract method/class/module, dependency inversion, constants extraction, and test-protected changes.
Use when writing or editing Python code. Enforces strict typing with basedpyright, ruff linting and formatting, modern Python 3.12+ idioms.
Use when writing tests for Python code. Covers pytest conventions, fixtures, mocking, strict type-checked tests.