From 3c6fc55b5de782e6e82b73744ae8f76d60be6e07 Mon Sep 17 00:00:00 2001 From: Saurav Panda Date: Wed, 18 Sep 2024 00:16:03 -0700 Subject: [PATCH 1/2] feat: updated work summary --- kaizen/llms/prompts/work_summary_prompts.py | 65 +++++++++++++-------- 1 file changed, 42 insertions(+), 23 deletions(-) diff --git a/kaizen/llms/prompts/work_summary_prompts.py b/kaizen/llms/prompts/work_summary_prompts.py index e35d38c0..4c3dd82f 100644 --- a/kaizen/llms/prompts/work_summary_prompts.py +++ b/kaizen/llms/prompts/work_summary_prompts.py @@ -15,46 +15,65 @@ """ WORK_SUMMARY_PROMPT = """ -Generate a user-friendly summary of the provided git diff for non-technical stakeholders. +Generate a concise summary of the provided git diff for daily/weekly standup reports. OUTPUT Format: {{ - "summary": "", - "details": ["", ...], - "todo": ["", ...], - "future_considerations": ["", ...], - "estimated_time": + "summary": "", + "details": ["", ...], + "in_progress": ["", ...], + "blockers": ["", ...], + "future_considerations": ["", ...], + "estimated_time": "" }} -estimated_time: its the range of time you think the above work might have taken for a developer. example "10-15hrs" -details: its list of changes in human readable term so that anyone can understand how the software has been impacted. +estimated_time_spent: Range of time spent on the work in hours, e.g., "5-7hrs" +completed_tasks: List of tasks completed, described concisely +in_progress: List of tasks currently being worked on +blockers: Any issues or dependencies preventing progress +next_steps: Immediate next actions or tasks to be tackled Guidelines: -1. Give a high-level overview of the goal. -2. Break down changes by file or area. -3. Explain in plain language, avoiding jargon. -4. Highlight new features, improvements, bug fixes, or optimizations. -5. Discuss impacts or benefits to the user or system. -6. Use examples or analogies for clarity. -7. Maintain a consistent, readable tone. +1. Provide a brief overview of the work done. +2. Focus on key accomplishments and progress. +3. Highlight any challenges or blockers encountered. +4. Keep descriptions concise and relevant to team updates. +5. Avoid technical jargon where possible. +6. Keep summaries concise and to the point. +7. All the points should be in human readable term. +8. Output should be in JSON format. PATCH DATA: {PATCH_DATA} """ MERGE_WORK_SUMMARY_PROMPT = """ -Merge all this information into the following output format. +Merge all this information into a consolidated standup report format. OUTPUT Format: {{ - "summary": "", - "details": ["", ...], - "todo": ["", ...], - "future_considerations": ["", ...], - "estimated_time": + "summary": "", + "details": ["", ...], + "in_progress": ["", ...], + "blockers": ["", ...], + "future_considerations": ["", ...], + "estimated_time": "" }} -estimated_time: its the range of time you think the above work might have taken for a developer in hours, be little generous. example "10-15hrs" -details: its list of changes in human readable term so that anyone can understand how the software has been impacted. +estimated_time_spent: Range of time spent on the work in hours, e.g., "5-7hrs" +completed_tasks: List of tasks completed, described concisely +in_progress: List of tasks currently being worked on +blockers: Any issues or dependencies preventing progress +next_steps: Immediate next actions or tasks to be tackled + +Guidelines: +1. Provide a brief overview of the work done. +2. Focus on key accomplishments and progress. +3. Highlight any challenges or blockers encountered. +4. Keep descriptions concise and relevant to team updates. +5. Avoid technical jargon where possible. +6. Keep summaries concise and to the point. +7. All the points should be in human readable term. +8. Output should be in JSON format. All the summaries: From 17813128ef4bf3fe40c7f146862825e9b14bd7a6 Mon Sep 17 00:00:00 2001 From: Saurav Panda Date: Wed, 18 Sep 2024 00:16:30 -0700 Subject: [PATCH 2/2] Clid app version update --- cli/pyproject.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cli/pyproject.toml b/cli/pyproject.toml index ec4df3d3..a47861da 100644 --- a/cli/pyproject.toml +++ b/cli/pyproject.toml @@ -1,6 +1,6 @@ [tool.poetry] name = "kaizen-cli" -version = "0.2.1" +version = "0.2.2" description = "" authors = ["Saurav Panda "] readme = "README.md"