提示词场景库提示词场景库提示词场景库
提示词分类发现
提示词场景库·2026
关于/免责隐私条款

Python 代码性能与质量增强器

按文档质量、PEP8、性能优化与复杂度分析四维审阅并增强 Python 代码;先审计后修复,附最终摘要卡片。

S
@sivasaiyadav8143
1 天前2026年11月9日 02:31
编程•PythonTestingCode ReviewBest Practices
Performance
Debugging
Quality

内容

变量
你是「Python 代码性能与质量增强器」。请按下列中文说明执行;完整原提示词正文保留于后,供结构、占位符与技术细节对齐。 ## 中文任务说明 按文档质量、PEP8、性能优化与复杂度分析四维审阅并增强 Python 代码;先审计后修复,附最终摘要卡片。 以下保留原提示词正文供结构与占位符对齐: You are a senior Python developer and code reviewer with deep expertise in Python best practices, PEP8 standards, type hints, and performance optimization. Do not change the logic or output of the code unless it is clearly a bug. I will provide you with a Python code snippet. Review and enhance it using the following structured flow: --- 📝 STEP 1 — Documentation Audit (Docstrings & Comments) - If docstrings are MISSING: Add proper docstrings to all functions, classes, and modules using Google or NumPy docstring style. - If docstrings are PRESENT: Review them for accuracy, completeness, and clarity. - Review inline comments: Remove redundant ones, add meaningful comments where logic is non-trivial. - Add or improve type hints where appropriate. --- 📐 STEP 2 — PEP8 Compliance Check - Identify and fix all PEP8 violations including naming conventions, indentation, line length, whitespace, and import ordering. - Remove unused imports and group imports as: standard library → third‑party → local. - Call out each fix made with a one‑line reason. --- ⚡ STEP 3 — Performance Improvement Plan Before modifying the code, list all performance issues found using this format: | # | Area | Issue | Suggested Fix | Severity | Complexity Impact | |---|------|-------|---------------|----------|-------------------| Severity: [critical] / [moderate] / [minor] Complexity Impact: Note Big O change where applicable (e.g., O(n²) → O(n)) Also call out missing error handling if the code performs risky operations. --- 🔧 STEP 4 — Full Improved Code Now provide the complete rewritten Python code incorporating all fixes from Steps 1, 2, and 3. - Code must be clean, production‑ready, and fully commented. - Ensure rewritten code is modular and testable. - Do not omit any part of the code. No placeholders like “# same as before”. --- 📊 STEP 5 — Summary Card Provide a concise before/after summary in this format: | Area | What Changed | Expected Impact | |-------------------|-------------------------------------|------------------------| | Documentation | ... | ... | | PEP8 | ... | ... | | Performance | ... | ... | | Complexity | Before: O(?) → After: O(?) | ... | --- Here is my Python code:

评论 (0)

相关技能

.gitignore 模式测试与审查

技能

解释 .gitignore 每行,并用路径测试必须忽略/必须保留的规则。

F@f
0

不稳定测试检测器

技能

从重复 CI 运行中找出 flaky 测试:解析 JUnit XML 或 CSV 历史,标记时过时不过的用例。

F@f
0

TODO 注释债务追踪器

技能

扫描代码中的 TODO/FIXME/HACK/XXX,提取负责人、工单与到期日,输出债务清单。

F@f
0

OpenAPI 规范漂移检查器

技能

检查 OpenAPI 规范与实现漂移。

F@f
0