Code Creation AI Prompts for Productivity
With Duo Agent Platform and Duo Chat we now have access to agents and tools that can make our processes more efficient. Here are some of the prompts we have collected to make this easier.
Generating Daily Standup Reports
Use Case / Impact
We post daily standup updates in Slack using Geekbot. We report on what we have done recently, what we plan to do, and if there are any blockers. Collecting this information can be time consuming and prone to missing information, even if we are doing this every day.
By having AI tools look through our recent activity, we can create a first draft of the report quickly.
We think this could save up to an hour per week (10-15 minutes per day) per engineer on the team.
Prompt
This prompt looks at your activity over the past 72 hours. This is likely more than we need, but it will catch multiple days like over a weekend. LLMs seem to have a hard time knowing the current time and do not know when you last updated your standup, so having a few days of activity will give us a good chance of catching all activity.
## Objective
Generate my daily standup summary by reviewing my GitLab activity from the past 72 hours.
## Query Strategy
1. Identify my GitLab user ID for filtering
2. Query merge requests (last 72 hours):
- `author_id=me` with states: merged, opened, closed
- `assignee_id=me` or `reviewer_id=me` with state: opened
3. Query commits authored by me in the last 72 hours
4. Query issues with my recent activity (assigned, commented, created) from last 72 hours
5. Fetch recent discussions/comments I've participated in within the last 72 hours
## Output Format
### What have you done since last report?
- Merged MRs with title and number
- Resolved or closed issues with brief context
- Code reviews completed (approved/commented on others' MRs)
- Commits pushed to active branches/MRs
- Progress on open MRs (addressed feedback, updated code)
### What will you do today?
- Continue work on open MRs (specify which ones and next steps)
- MRs assigned to me for review
- Issues to investigate or start
- Follow-ups needed from yesterday's work
- Meetings or planning sessions related to development work
### Anything blocking your progress?
- MRs waiting on reviews from others (include reviewer names)
- Blocked MRs with external dependencies
- Stalled reviews (no activity \> 2 days)
- Waiting on decisions or clarifications
- Technical blockers or access issues
## Formatting Guidelines
- Use bullet points with 1-2 sentances per item
- Do not use sub-bullets
- Always include MR/issue numbers (!XXXX, #XXXX)
- Bold important status indicators (**BLOCKED**, **Failing CI**)
- Group related activities for the same feature
- Include metrics where helpful (e.g., "1 approval received")
a46c5bb8)
