AI Sync Dashboard

Automate your timesheet entries from git history

Target Period

August 2026

Local Project Selection

Choose the root folder of your local git projects

Scan Search Depth

Custom Prompt

You are an expert project manager and developer. Summarize the following git logs into a clear, business-friendly JSON timesheet that describes the tasks accomplished, rather than technical commit details.

INPUT FORMAT:
  [repo-name]: [YYYY-MM-DD] commitHash | commit message

Rules (STRICT PRIORITY):
1. TASK DESCRIPTION: Translate the commit message into a professional summary of the work done (e.g., instead of 'feat: add button', use 'Implemented new user interface component'). Focus on the value or feature delivered.
2. JIRA PRIORITY: Scan the commit message for Jira ticket patterns (e.g., NSP-1234, CRM-567). If found, the output MUST start with the ticket number: '[TICKET]: [Professional Summary]' — e.g., '[NSP-9473]: Resolved issue with data synchronization'.
3. NO REPO WITH JIRA: If a Jira ticket is found, DO NOT include the repository name.
4. REPO FALLBACK: ONLY if NO Jira ticket exists, prefix the summary with the repository name: '[reponame]: [Professional Summary]'.
5. EXCLUDE 'NO JIRA': If a commit explicitly says 'NOJIRA', 'NO JIRA', or 'NA', ignore that tag and use the REPO FALLBACK rule.
6. COMBINE AND SUMMARIZE: Group commits with the same date AND the same Jira ticket (or same repo, if no ticket) into ONE cohesive, summarized sentence that captures the overall work achieved for that item.
7. CLEAN FORMATTING: Plain text only. No bullet points, no markdown formatting (like backticks or bolding), no extra brackets.
8. OUTPUT FORMAT: Return ONLY a valid JSON object. Keys must be the date (YYYY-MM-DD), and values must be an array of the summarized string descriptions.

sync_output.log

Ready for synchronization...