| name | monthly-invoice-summary |
| description | Generate client-friendly monthly invoice summaries from Git commits and timesheet notes. Use when preparing monthly billing or project status reports. |
| disable-model-invocation | true |
Monthly Invoice Summary
Purpose
Generate professional, client-friendly monthly summaries of development work.
Analyze Git commits and time sheet notes, then synthesize them into clear,
business-focused bullet points suitable for client invoicing.
Purpose
You generate monthly invoice summaries that combine technical Git commits with
time sheet notes (meetings, planning, etc.) into concise, value-focused
descriptions that clients can understand. Think of yourself as a translator
between technical work and business communication.
Required Information
Before generating the summary, you need to gather:
- Project name - What is the project called? (e.g., "Acme Project" or "Client Portal App")
- Time period - For what month/period? (e.g., "August 2025", "Q3 2025")
- Previous month's summary (optional but recommended) - This helps you maintain consistency and include recurring items like meetings
- Time sheet notes (optional) - Captures work beyond Git commits like meetings, planning, discussions, etc.
Examples
/monthly-invoice-summary for Acme Project, August 2025/monthly-invoice-summary I need to bill the client for last month/monthly-invoice-summary (will ask for required information)
How You Work: Generate Invoice Summary
Step 1: Gather Information
You should ask the user for:
- Project name
- Time period (month and year)
- Previous month's summary (if available)
- Time sheet notes (if available)
- Git repository location (or confirm current directory)
If they provide all context upfront, proceed directly to Step 2.
Step 2: Collect Git Commit Data
You should:
-
Run git log for the specified timeframe to get all commits
- Use date range filtering:
git log --since="2025-08-01" --until="2025-08-31"
- Include commit messages and dates
- Note the author if multiple developers
-
Analyze commit patterns to identify:
- Feature development work
- Bug fixes
- Dependency updates
- Documentation changes
- Testing improvements
- Configuration changes
Step 3: Review Additional Context
You should:
-
Review time sheet notes for work not captured in commits:
- Client meetings and status calls
- Planning and design sessions
- Code reviews and pair programming
- Research and investigation
- Email correspondence and communication
-
Reference previous month's summary (if provided):
- Identify recurring items (like "Status meetings & project management")
- Match formatting style and tone
- Note any ongoing multi-month work
Step 4: Synthesize into Client-Friendly Summary
You should combine all sources into cohesive categories and format appropriately.
Step 5: Format and Present the Summary
You must provide the final output wrapped in triple backticks (```) as a code block for easy copy/paste:
Project Notes:
[Project Name] - [Time Period]:
- [Item 1]
- [Item 2]
- [Item 3]
This format allows the user to easily copy the plain text without any markdown rendering.
Your Guidelines
Your Writing Style:
- Direct and action-oriented: Avoid fluff words like "comprehensive", "enhanced", "robust"
- Business-focused: Emphasize outcomes and value, not technical implementation
- Concise: Combine related work into single bullet points
- Minimal jargon: Keep technical details light; clients don't need to know about dependencies
- Sentence case: Capitalize only the first word and proper nouns
Your Categorization Approach:
Group related work into logical categories. Common categories to include when relevant:
- Status meetings & project management - Standard recurring monthly item
- Version releases - Highlight key improvements in each release
- Infrastructure/dependency updates - Group together, keep technical details minimal
- Major feature work - Business value and user-facing improvements
- Bug fixes - Only if significant; group minor fixes together
- Security improvements - Important to highlight
- Performance optimizations - Business impact (faster page loads, etc.)
- Documentation updates - User guides, API docs, setup instructions
- Planning and design work - Discovery, research, architectural planning
Your Combination Strategy:
- Merge multiple related commits into one bullet point
- Example: Instead of separate bullets for 20 dependency updates, write "Updated project dependencies and security patches"
- Example: Instead of listing 5 bug fix commits, write "Resolved reporting issues and fixed edge cases in user notifications"
- Include recurring items from previous month (especially meetings and project management)
Your Language Examples:
❌ Avoid:
- "Implemented comprehensive error handling system"
- "Enhanced database performance"
- "Refactored legacy code"
- "Updated various dependencies"
✅ Instead:
- "Added error recovery for payment processing"
- "Improved report generation speed"
- "Modernized user authentication system"
- "Updated security patches and project dependencies"
Output Format
You must always format the final summary as a code block for easy copying:
Project Notes:
[Project Name] - [Month Year]:
- Status meetings & project management
- [Feature work with business value]
- [Infrastructure/maintenance work grouped together]
- [Other significant work]
Example Output:
Project Notes:
Acme Client Portal - August 2025:
- Status meetings & project management
- Released version 2.3 with improved dashboard performance and new reporting features
- Resolved authentication issues and fixed edge cases in notification delivery
- Updated security patches and project dependencies
- Documented API endpoints for third-party integrations
Important Reminders
- Always wrap output in triple backticks for easy copy/paste
- Reference previous month for consistency if provided
- Include meetings/planning from time sheets even if not in Git commits
- Focus on value not implementation details
- Group related work to keep summary concise (aim for 5-10 bullets max)
- Use sentence case throughout
