groove-utilities-memory-log-daily

Included with Lifetime

$97 forever

Write the daily memory log entry. Use at end of day to record what happened.

General

What this skill does


# groove-utilities-memory-log-daily

## Outcome

`.groove/memory/daily/YYYY-MM-DD.md` is created or updated with a structured end entry. The file may already exist from daily start (start-of-day structure); if so, append the closeout sections. The file is written so that the next daily start can verify yesterday had an end.

## Acceptance Criteria

- File exists at `.groove/memory/daily/YYYY-MM-DD.md` after command completes
- "Done today" section contains granular multi-level bullets sourced from completed tasks and git diff
- Git section summarises commits and changed files for the day
- Tasks section shows task summary by status
- Learnings section is populated (not blank)
- Open/Next section captures carry-forward items
- If file already exists, content is updated/appended rather than overwritten

## Constraints

- Memory path is always `.groove/memory/`
- Write at daily end only — never called at daily start. File may already exist from daily start; append closeout sections rather than overwriting.
- "Done today" must be sourced from: completed tasks (date-matched) and `git diff` output — not from incomplete work
- **Pending capture**: if `.groove/.cache/pending-capture.md` exists (staged by the `session-capture` Stop hook), use it to pre-fill the "Done today" and "Git" sections — its commits/working-changes are the raw material, so the user reviews and edits a draft rather than starting blank. After the daily log is written successfully, delete `.groove/.cache/pending-capture.md`.
- If a completed task has no resolution in its body, ask user for a summary before writing the bullet
- Use template at `skills/groove-utilities-memory-log-daily/templates/daily.md` for file structure
- If the directory `.groove/memory/daily/` does not exist, create it before writing
- Vague entries ("worked on stuff") should trigger a clarification ask before writing

Files: 2

Size: 2.3 KB

Complexity: 11/100

Category: General

Source: https://github.com/andreadellacorte/groove/tree/main/skills/groove-utilities-memory-log-daily

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts