Automatisch Änderungszusammenfassung für Git-Projektcommits

Heim

KI-Prompt-Liste

Automatische Zusammenfassung GitHub Commits

${:__('collect %s',Automatische Zusammenfassung GitHub Commits)}$

Erstellt eine klare, prägnante Änderungszusammenfassung aus der GitHub-Commit-Historie eines Softwareprojekts, sortiert Kernänderungen von Versionen, damit das Entwicklerteam den Projektfortschritt abgleichen kann.

Prompt-Inhalt

Kopieren

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.

Kopieren

Gehen Sie alle Commits der letzten zwei Wochen eines angegebenen GitHub-Repositorys durch, ordnen Sie die Änderungen drei Kategorien zu: neue Funktionen, Fehlerbehebungen und Architekturanpassungen, und schreiben Sie eine verständliche Zusammenfassung in natürlicher Sprache für das wöchentliche Meeting des Projektteams, vermeiden Sie Entwicklerjargon und behalten Sie eine einfache Sprache bei.

Kopieren

Teilen Klicken Sie, um den Link zu kopieren

Kommentare (0)

0/300

Einreichen

Empfehlung

E-Com Ticket-Klassifizierer

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 Ticket-Klassifizierung

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-Ticket-Klassifizierer

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.

E-Commerce-Ticket-Klassifizierer

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.

E-Commerce-Ticket-Klassifizierung

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.

E-Commerce-Support-Ticket-Klassifizierung

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.