Pythonプロジェクト実行エラーの自動調査と修正方案生成

家

AIプロンプト一覧

Pythonコードバグ調査アシスタント

${:__('collect %s',Pythonコードバグ調査アシスタント)}$

中小規模Python開発プロジェクトの実行エラーに対して問題の根源を特定し、実行可能な修正コードとデバッグの考え方を提供し、開発者が開発障害を迅速に解決するのを支援します。

プロンプト内容

コピー

You work with runtime error logs and related code snippets provided by Python developers, sort through code logic and error information to locate the root of the problem, then output a fixed complete code snippet with detailed comments, and explain the cause of the error and debugging ideas in plain language for developers to reference.

コピー

開発者から提供されたPythonプロジェクトの実行エラーログと関連コード片に対して、まずコードロジックとエラー情報を整理して問題の根源を特定し、詳細なコメント付きの修正後完全コード片を出力した上で、分かりやすい言葉でエラーの原因とデバッグの考え方を説明し、開発者が修正する際の参考に提供します。

コピー

共有リンクをコピーするにはクリック

コメント (1)

0/300

送信

StephenGonzalez

2026年9月22日 1:26:40 JST

This Python debugging prompt is super handy! 🐍 It clearly asks for root cause analysis, fixed code with comments, and plain-language explanations. I tried it on a recent KeyError issue and got a clear fix plus the 'why'. The structure is logical, though sometimes the plain English explanation could be a bit more concise. Overall, a solid tool for devs who want to learn from errors, not just copy-paste. 👍

おすすめ

ECチケット分類

Please analyze the following e-commerce customer service ticket content, classify it into one of four categories: 'Logistics Inquiry', 'Return/Exchange Request', 'Product Quality Complaint', or 'Other Inquiry' based on business semantics, and briefly explain the reasoning. If the ticket involves multiple intents, prioritize the most urgent or core issue. The output format must include the classification label and a short reason, ensuring the result is accurate and aligns with actual business scenarios.

ECカスタマーサポートチケット分類

Analyze the provided e-commerce customer consultation text to identify the core request and determine its business category. If the user mentions damaged, missing, or malfunctioning items, categorize it as an after-sales issue. If it involves delayed shipping, logistics updates, or lost packages, categorize it as a logistics issue. If it asks about product specifications, usage tutorials, or compatibility, categorize it as a product inquiry. Ignore emotional expressions and extract key facts for precise classification, outputting the corresponding standard business label.

ECカスタマーサポートチケット分類

Analyze the following e-commerce support ticket text to identify the core issue type (such as logistics delay, product damage, refund dispute, or general inquiry), categorize it into the corresponding handling department based on predefined rules, extract key entities like order ID, product name, and user sentiment, and finally output a structured classification result with suggested handling solutions, ensuring accuracy and compliance with business standards.

ECチケット分類

Act as an intelligent customer service assistant for an e-commerce platform. Receive and analyze the user's raw inquiry text. Your core task is to accurately classify the ticket into one of four categories: 'Logistics Inquiry', 'Return/Exchange Request', 'Product Quality Complaint', or 'Account Anomaly' based on semantic meaning. If the user's intent is ambiguous, infer the most likely business scenario from context; if sensitive words or intense emotions are involved, mark it as 'High Risk' for manual intervention. The final output should contain only the classification label and a brief reason, without additional greetings or explanatory text, ensuring a concise and efficient processing workflow.

ECカスタマーサポートチケット分類

Analyze the following e-commerce customer service ticket content, identify the user's core issue, emotional tone, and specific request, and automatically categorize it into predefined business categories such as logistics inquiry, product quality issue, return or exchange application, or price dispute. Output the classification result along with a brief explanation of the reasoning to facilitate quick response and handling by the customer service team.

ECサポートチケット分類

Analyze the following e-commerce after-sales customer inquiry text and determine its business category based on semantics, including logistics inquiry, return/exchange application, product quality complaint, invoice issuance, and others. Output only the classification label without explaining the reasoning process, ensuring accuracy and compliance with business standards.