开发与测试
python
Write clean, readable Pythonic code. Use this skill any time you write or change a Python file.
kissgyorgy · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add kissgyorgy/coding-agents --skill python技能说明
name: python description: Write clean, readable Pythonic code. Use this skill any time you write or change a Python file.
General guidelines
Coding Style
- Always write clean, readable, well separated, well organized, Pythonic code.
- Don't run linters or formatters, they will run automatically after every edit by the harness.
- When using
datetime, import it like this:import datetime as dt - CRITICAL: ALWAYS put ALL imports at the top of the file, NEVER inside
functions, methods, or any other block. No exceptions. Use
TYPE_CHECKINGguard for type-only imports to avoid circular dependencies.
Type hints
- ALWAYS type hint every function and method signature precisely even in tests.
- NEVER write "-> None" type hint for return values, they are not necessary.
- No need to type hint variables from functions call return values inside function bodies, they are inferred from the method return type, except extreme cases when the type is a huge help or a generic and it's concrete type cannot be determined.
- Only use APIs, class names, variables or objects which you already read or know exist for sure.
- Use the new pipe operator for
Optionalvariables like this:value | None - Use
Anyfor "all types" instead ofobject.
Testing
- ALWAYS use
pytestfor all tests - ALWAYS assert on whole ouptut or full results in tests, not just tiny parts
- For mocking, use pytest
monkeypatchfixture, NEVERunittest.mockand NEVER any of theMockclasses orpatchfunction - IMPORTANT: NEVER import from
conftest.py - ALWAYS type hint test function parameters correctly.
- Don't make a test class with only one function, a module-level test function is enough
- NEVER use
unittest.mockor any of theMockclasses orpatchfunction, never assert on method calls, use real objects and assert on full results. When absolutely necessary and can't be avoided, usepytest.monkeypatch, when the test setup would be too difficult or the code have side effects, but consider writing a fake. - ALWAYS assert on the full result of the function call, never just list lengths or containment, except where that's the point.
Managing dependencies
- Use
uv addfor adding dependencies, never directly editpyproject.tomlfiles. - For CLI scripts and apps, ALWAYS use
clicklibrary instead ofargparse, add it to dependencies if necessary.