Feed

Standup update from my git log

Asha Rao@asha_rao
Remix
The prompt

Here's my git log since yesterday's standup:

[paste git log --oneline --since=yesterday]

Write my standup update in three lines: Done, Doing, Blocked. Group related commits, use plain words instead of commit jargon, and leave Blocked as "Nothing" if there's nothing in the log that suggests a blocker.

190 uses70 saves52 likes0 remixesPublished 2 Oct 2026

A use is a copy, a fill-in copy, an insert or an open in an AI chat, counted once per person per day. Authors' own uses don't count.

More like this

Here are my raw notes from meeting. List every decision we made, who owns it and the deadline. Put open questions in a separate list. If nobody was named as owner, write "unassigned"; don't guess. Keep each item to one line. Then write a three-line summary I can paste into Slack channel for people who weren't there. Notes: paste notes
Daniel Okafor1,960 uses
Write test framework tests for the function below. Cover the happy path, the boundaries, invalid input, and one property that should always hold. Use test names that read as sentences. Don't mock what you don't own. If the function is hard to test, suggest the smallest refactor that would help. paste function
Arjun Mehta720 uses
Explain this language module to a new teammate who knows the language but not our codebase. Start with what it's for in one sentence, then the main flow, then the two things most likely to trip them up. Point to functions by name. Finish with a Mermaid sequence diagram of the call flow. paste code
Daniel Okafor510 uses
Here are my raw notes from meeting. Turn them into: 1. A decision log: decision, owner, deadline. Write "unassigned" when no owner was named. 2. A RACI table for each decision (Responsible, Accountable, Consulted, Informed), using only names that appear in the notes. 3. A list of open questions. Flag any decision that has two Accountable people. Notes: paste notes
Meera Iyer380 uses
Turn the document below into a number-slide outline for audience. They have minutes minutes and need to decide decision. For each slide: a title that states the point as a full sentence (not "Overview" or "Results"), three bullets of evidence from the document, and one line of speaker notes. Put the decision you're asking for on slide 2, not the last slide. Leave out anything they don't need to make the decision. paste document
Save My Prompts2,210 uses
Review this diff as a careful senior engineer. Look in this order: correctness bugs, security issues, data loss or migration risks, then performance. Skip style nits unless they hide a bug. For each finding give the file and line, what's wrong and a concrete fix. If something is fine but non-obvious, say why it's fine. End with Ship, Ship after fixes or Don't ship, and one sentence why. Context: what the change is supposed to do paste diff
Arjun Mehta1,730 uses
Advertisement
Ad slot (preview)Display · responsiveShown only after AdSense approval and consent