groove-daily-start
Start the workday: review yesterday, create today's daily memory, load tasks, prepare agenda. Use when beginning the day.
What this skill does
# groove-daily-start
## Outcome
The workday is prepared: recent days are reviewed, today's daily memory file is created, tasks are consolidated and presented, and the user knows what to work on.
## Acceptance Criteria
- Yesterday's daily memory file is reviewed (summary shown; warn if missing or no end section)
- Today's daily memory file is created with a start-of-day structure (if it does not already exist)
- Task list is loaded and presented (grouped by status)
- User has a clear picture of the day's agenda before starting work
## Constraints
- Read `.groove/index.md` for `tasks.backend` and `memory.review_days` config
- Memory path is always `.groove/memory/`
- Call `/groove-utilities-task-analyse` to get current task state
- **Review recent days:** If `.groove/memory/daily/` is empty (no files exist), skip this step entirely and note "Fresh install — no prior logs." Otherwise, identify the last `memory.review_days` business days (Mon–Fri) counting back from yesterday (skip Saturday and Sunday). For each date:
- Check `.groove/memory/daily/YYYY-MM-DD.md`:
- `✓ YYYY-MM-DD — start + end logged` if both start-of-day and end sections exist
- `~ YYYY-MM-DD — start only, no end logged` if only start section present
- `✗ YYYY-MM-DD — missing` if file does not exist
- Show a one-line context from the file if present (e.g. first bullet from "Done today" or plan intent)
- Show git activity: run `git log --oneline --after="YYYY-MM-DD 00:00" --before="YYYY-MM-DD 23:59:59"` — display commit count and first few titles; skip silently if not in a git repo or no commits
- Do NOT block start if files are missing or incomplete — just report
- **Create new day memory:** Create today's file at `.groove/memory/daily/YYYY-MM-DD.md` using the template at `skills/groove-daily-start/templates/daily-start.md`. If the file already exists, skip (idempotent). Create `.groove/memory/daily/` if missing.
- After the recent-days review, check for open promises via `/groove-utilities-memory-promises --list`:
- If open promises: show inline note: `→ N open promise(s) — run /groove-utilities-memory-promises --list to review`
- If none: skip silently
- After the recent-days review, check for open mistake incidents via `/groove-utilities-memory-mistakes --list`:
- If open incidents: show inline warning: `⚠ N open incident(s) — resolve at next /groove-work-compound`
- If none: skip silently
- Do NOT modify tasks during start
- Present task list in a scannable format before the user begins
- After all standard steps: check if `.groove/hooks/start.md` exists
- If it exists: read the `## Actions` section and execute each item in order; report completion per item
- If it does not exist: skip silently
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.