家
GitHubコミット記録の自動サマリー生成
AI
37
37
ソフトウェアプロジェクトのGitHubコミット履歴から明確で簡潔な変更サマリーを生成し、バージョンアップのコア変更内容を整理して、開発チームのプロジェクト進捗共有を支援します。
プロンプト内容
コピー
コピー
Sort through all commit records from the past two weeks of a specified GitHub repository, organize all changes into three categories: new features, bug fixes and architecture adjustments, and write an easy-to-understand natural language summary for the project team's weekly meeting, avoid jargon and keep the language straightforward.
コピー
指定されたGitHubリポジトリの過去2週間のすべてのコミット記録を整理し、機能追加、不具合修正、アーキテクチャ調整の3つのカテゴリに分けてすべての変更をまとめ、開発チームの週次会議で共有するための、わかりやすい自然言語のサマリーを作成してください。開発専門用語を使わず、平易な言葉にしてください。
コピー
コメント (0)
0/300
おすすめ
ECチケット分類
Analyze the following customer service message from an e-commerce platform and determine its business category. The possible categories are: Logistics Inquiry, Return/Exchange Request, Product Quality Issue, Price Dispute, or Other Inquiry. Output only the category name without any explanation or additional text. If the message cannot be clearly classified, output 'Other Inquiry'.
ECチケット分類
Act as a data analysis assistant for an e-commerce customer service system. Read the current list of pending customer inquiry tickets, automatically categorize them into four major categories based on the nature of the issue: logistics inquiry, product quality, return/exchange application, or complaint/suggestion. Extract key entities such as order numbers, product SKUs, and user sentiment tendencies, and finally output structured classification results for subsequent manual review or automatic routing.
ECチケット分類
Act as an intelligent customer service assistant for an e-commerce platform. Receive the raw text of a user's inquiry, analyze its core intent and urgency, and categorize it into one of four types: pre-sales consultation, after-sales rights protection, logistics inquiry, or complaint/suggestion. Extract key entities such as order numbers, product names, and problem descriptions. Finally, output a structured classification result and handling suggestions, ensuring the response is accurate and complies with corporate customer service standards.
ECチケット分類
Please analyze the following e-commerce customer service ticket content and classify it into one of four categories: 'Logistics Inquiry', 'Return/Exchange Request', 'Product Quality Complaint', or 'Other Inquiry' based on predefined business rules. If the ticket involves multiple issues, prioritize the most urgent or core issue category. Ensure the classification result is accurate and aligns with actual business scenarios to enable the customer service team to respond quickly.
ECチケット分類
Please analyze the following e-commerce customer inquiry ticket content, automatically 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 classification basis to enable the customer service team to respond and handle it quickly.
ECカスタマーサポートチケット分類
Analyze the provided customer inquiry text and categorize it into one of four predefined classes: pre-sales consultation, after-sales service, logistics inquiry, or complaint/suggestion based on business semantics. If an order number is mentioned, extract it; if emotional expression is present, label the sentiment as positive, neutral, or negative. The output must include the classification result, key entity extraction, and sentiment label, ensuring the logic aligns with standard e-commerce customer service protocols without additional explanatory reasoning.
