Understand the PyCharm project
Identify interpreters, virtual environments, source roots, modules, framework support, run configurations, environment variables, and code style.
PyCharm Codex Skills help Codex work with the Python project you already manage in PyCharm. Download the skills for interpreter setup, dependency files, run and debug configurations, inspections, refactoring, pytest, Django, notebooks, remote environments, and project-aware verification.
task: complete python development in pycharm task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffPyCharm organizes coding, inspections, refactoring, running, debugging, testing, and version control around a project and its selected environment.
These skills make Codex inspect that project context before changing code, then verify the result with the same commands and configurations the developer relies on.
Identify interpreters, virtual environments, source roots, modules, framework support, run configurations, environment variables, and code style.
Create modules, add type hints, resolve imports, apply project conventions, and plan structural changes with usage-aware checks.
Use the correct entry point, debugger context, logs, breakpoints, stack traces, inspections, and problem reports to isolate failures.
Run focused tests, full suites, linters, type checkers, coverage, framework checks, and the configured pre-commit process.
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
Confirm interpreter, dependency manager, Python version, framework, folders, commands, test runner, and generated-file boundaries.
Locate the entry point and affected symbols, inspect callers and tests, and define the expected result before editing.
Preserve imports, types, framework patterns, configuration, and public behavior while updating the smallest coherent area.
Execute the relevant run or test configuration, inspect failures and coverage, then report changed files and remaining risks.
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Work on scripts, packages, services, command-line tools, desktop programs, and reusable libraries.
Support Django, Flask, FastAPI, templates, migrations, routes, settings, and framework tests.
Handle scientific packages, Jupyter notebooks, data files, plots, and reproducible environments.
Respect Docker, WSL, SSH, remote interpreters, deployment mappings, and environment-specific commands.
Start with one defined outcome and provide the source material, constraints, and checks that matter.
These skills are designed for people who need dependable python development in pycharm work with a visible process.
Keep Codex aligned with the interpreter, style, framework, and checks used in PyCharm.
Develop routes, models, migrations, services, tests, and configuration with project context.
Maintain notebooks, environments, packages, data paths, and reproducible analysis code.
Coordinate local editing with containers, WSL, SSH interpreters, and deployment targets.
The skills can guide project work and run available commands, but they cannot operate an unseen PyCharm UI, recover missing credentials, or prove behavior in an unavailable remote interpreter.
Install the complete skill folder and add the project-specific context before beginning.
Keep SKILL.md with project discovery, interpreter, debugging, refactoring, testing, and verification guidance.
Use repository scope so the workflow can follow project files, dependency locks, style rules, and test settings.
Record Python and PyCharm versions, interpreter type, framework, package manager, run commands, and remote setup.
Add the exact test, lint, type, framework, coverage, and packaging commands used before completion.
Practical answers about capabilities, limits, setup, and review.
They can prepare or explain project files and settings where those are accessible, but interactive IDE changes may still need you to confirm them.
Yes. They inspect the configured runner and use focused or full test commands appropriate to the project.
Yes, including settings, models, views, migrations, templates, management commands, and tests.
They first identify the intended interpreter and dependency setup instead of assuming the system Python is correct.
Yes. Provide the traceback, inputs, run configuration, environment, and reproducible command so the workflow can test its diagnosis.
Clear context. Purposeful work. Relevant checks. A result others can understand.