standup
Generates a casual, human-sounding daily standup from your git activity in the last 24 hours. Make sure to use this skill whenever the user says "standup", "daily standup", "write my standup", "what did I do yesterday", "write my daily update", or invokes /standup — even if they just ask "can you write my standup?"
What this skill does
# Daily Standup Generator
Transform git history into a human standup update. Nobody cares about commit
messages — translate them into what you actually accomplished.
## Step 1 — Fetch Git Activity
```bash
git log --since="24 hours ago" --author="$(git config user.email)" --oneline
```
If multiple repos are relevant, run in each. If no commits: skip to Step 3.
## Step 2 — Transform Commits into Accomplishments
Map raw commit messages → casual language. The rule: write what you'd say
out loud to a teammate, not what you typed in the terminal.
| Raw commit | Translated |
|---|---|
| `feat(modal): add purchase modal skeleton` | Shipped the purchase modal skeleton |
| `fix: resolve pagination bug` | Finally got that pagination bug squashed |
| `refactor: migrate to React Query` | Got the React Query migration working |
| `chore: update dependencies` | Bumped deps (skip — not worth a bullet) |
| `docs: update README` | Updated the README (skip unless it's notable) |
**Rules:**
- Active verb first: "Shipped", "Fixed", "Got X working", "Finished", "Wired up"
- Specific beats vague: "modal skeleton" not "UI changes"
- Skip pure chores (dep bumps, lint fixes) unless something broke
- If multiple commits touch the same thing, merge into one bullet
- Highlight if you unblocked teammates: "Reviewed and merged X's PR"
## Step 3 — Handle No Commits
If no commits in 24h, say:
```
Yesterday I:
- Focused on code reviews and planning
```
Never invent fake accomplishments. Don't mention the absence of commits.
## Step 4 — Infer "Today I Plan To"
In order of preference:
1. Current branch name: `git branch --show-current` → parse intent
- `feat/payment-flow` → "Continue the payment flow"
- `fix/auth-timeout` → "Fix the auth timeout issue"
2. If branch name is unclear, ask: "What are you working on today?"
3. If user is reluctant, offer: "I can leave the Today section for you to fill in"
## Output Format
```
Yesterday I:
- [Accomplishment — active verb, specific]
- [Accomplishment 2]
Today I plan to:
- [Inferred from branch or asked]
Blockers: [None, or specific blocker if mentioned]
```
Omit Blockers line if there are none.
## Style Rules
- Casual, not corporate. "Shipped" not "Implemented". "Fixed" not "Resolved".
- 3–5 bullets total across both sections
- No bullet should exceed one line
- Don't add preamble ("Here's your standup:") — just the standup
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.