admin/scribe
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add ATTENDANCE section to summary prompt
Mirror and run GitLab CI / build (push) Has been cancelled
Details
Ruff / ruff (push) Has been cancelled
Details

Browse Source
This commit is contained in:
admin
2026-06-20 16:41:08 +00:00
parent 44bf935d70
commit a545995221
1 changed files with 21 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scraibe/summarizer.py
+20 -9
View File
@@ -195,7 +195,8 @@ class SummarizerClient:
"- Key points and arguments\n" "- Key points and arguments\n"
"- Decisions and agreements\n" "- Decisions and agreements\n"
"- Action items and responsibilities\n" "- Action items and responsibilities\n"
"- Any risks, conflicts, or open issues\n\n" "- Any risks, conflicts, or open issues\n"
"- Names, roles, or affiliations of speakers (when mentioned)\n\n"
"Be concise but complete. Use bullet points where helpful. " "Be concise but complete. Use bullet points where helpful. "
"Do not add information that is not present in the transcript." "Do not add information that is not present in the transcript."
) )
@@ -203,17 +204,27 @@ class SummarizerClient:
return ( return (
"You are an expert legal and business meeting summarizer. " "You are an expert legal and business meeting summarizer. "
"You will receive several intermediate summaries of a longer conversation. " "You will receive several intermediate summaries of a longer conversation. "
"Produce a single, comprehensive summary that makes it clear: " "Produce a single, comprehensive summary using markdown. "
"- The overall purpose and context of the discussion\n" "Structure your response with the following sections:\n\n"
"- The main issues and topics addressed\n" "1. ATTENDANCE\n"
"- Key arguments and positions (briefly)\n" "- List all participants whose names or roles can be identified from the conversation.\n"
"- Decisions and outcomes\n" "- If a name is not given, use their role/position (e.g., Judge, Client, Manager, Witness) or 'Speaker 1', etc.\n"
"- Action items, responsibilities, and next steps\n" "- Keep it concise.\n\n"
"- Any unresolved issues or risks\n\n" "2. PURPOSE AND CONTEXT\n"
"- Briefly state the overall purpose and context of the discussion.\n\n"
"3. MAIN ISSUES AND TOPICS\n"
"- Summarize the main issues and topics addressed.\n\n"
"4. KEY ARGUMENTS AND POSITIONS\n"
"- Briefly outline key arguments and positions taken by each party.\n\n"
"5. DECISIONS AND OUTCOMES\n"
"- Clearly list decisions made and outcomes reached.\n\n"
"6. ACTION ITEMS AND NEXT STEPS\n"
"- List all action items, responsibilities, and next steps.\n\n"
"7. UNRESOLVED ISSUES AND RISKS\n"
"- Note any unresolved issues, conflicts, or risks.\n\n"
"The summary should be detailed enough that a reader who was not present " "The summary should be detailed enough that a reader who was not present "
"can understand what happened and what is expected going forward. " "can understand what happened and what is expected going forward. "
"Use clear, concise language and bullet points where appropriate." "Use clear, concise language and bullet points where appropriate."
"Use markdown formatting (headings, lists, bold) to structure the summary."
) )
def _summarize_chunk(self, chunk: str, index: int, total: int) -> str: def _summarize_chunk(self, chunk: str, index: int, total: int) -> str: