fix(0.11.1): daily end no git commit; do not modify tasks in start/end

Made-with: Cursor

Author: andreadellacorte

.groove/index.md

@@ -1,7 +1,8 @@
 ---
-groove-version: 0.10.0
+groove-version: 0.11.0
 tasks: beans
 memory: .groove/memory/
+recent_memory_days: 5
 git:
   memory: commit-all
   tasks: commit-all

CHANGELOG.md

@@ -2,6 +2,12 @@
 
 All notable changes to groove will be documented in this file.
 
+## [0.11.1] - 2026-03-05
+
+### Changed
+- `groove-daily-end`: removed in-skill git commit behaviour — no longer stages or commits; use `.groove/hooks/end.md` for commit actions if desired. Constraint "Do NOT archive tasks" replaced with "Do NOT modify tasks during end".
+- `groove-daily-start`: constraint "Do NOT archive tasks" replaced with "Do NOT modify tasks during start"; task-analyse call moved to top of Constraints.
+
 ## [0.11.0] - 2026-03-04
 
 ### Changed

skills/groove-daily-end/SKILL.md

@@ -20,27 +20,19 @@ The workday is wrapped up: git changes are analysed, memory files are written in
 - Weekly memory file written if today is the last weekday of the week
 - Monthly memory file written if today is the last weekday of the month
 - Tasks are analysed and summary is included in daily memory
-- Changes committed for any component whose git strategy allows it
 
 ## Constraints
 
 - Read `.groove/index.md` for `tasks:`, `memory:`, and `git.*` config
+- Call `/groove-utilities-task-analyse` to get task summary for daily memory population
 - Memory population order (must follow this sequence):
   1. `/groove-utilities-memory-log-git`
   2. `/groove-utilities-memory-log-daily`
   3. `/groove-utilities-memory-log-weekly` (only if last weekday of week, or explicit request)
   4. `/groove-utilities-memory-log-monthly` (only if last weekday of month, or explicit request)
-- Call `/groove-utilities-task-analyse` to get task summary for daily memory population
-- Do NOT archive tasks during end — that is user-triggered only
-- Git commit strategy (per component):
-  - `git.memory: ignore-all` — do not stage memory files
-  - `git.memory: hybrid` — stage `<memory>/` files (sessions are gitignored, logs are committed)
-  - `git.memory: commit-all` — stage `<memory>/` files
-  - `git.tasks: commit-all` — stage `.groove/tasks/` files
-  - `git.hooks: commit-all` — stage `.groove/hooks/` files
-  - If any files were staged: commit with message `YYYY-MM-DD end`
-  - If nothing to stage: skip commit silently
+
 - Last weekday detection: use local calendar date; handle gracefully if run on weekend
+- Do NOT modify tasks during end
 - After all standard steps: check if `.groove/hooks/end.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

skills/groove-daily-start/SKILL.md

@@ -23,6 +23,7 @@ The workday is prepared: recent days are reviewed, today's daily memory file is
 ## Constraints
 
 - Read `.groove/index.md` for `tasks:`, `memory:`, and `recent_memory_days:` config
+- Call `/groove-utilities-task-analyse` to get current task state
 - **Review recent days:** Identify the last `recent_memory_days` business days (Mon–Fri) counting back from yesterday (skip Saturday and Sunday). For each date:
   - Check `<memory>/daily/YYYY-MM-DD.md`:
     - `✓ YYYY-MM-DD — start + end logged` if both start-of-day and end sections exist
@@ -32,8 +33,7 @@ The workday is prepared: recent days are reviewed, today's daily memory file is
   - 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:** Call `/groove-utilities-memory-init-daily` to create today's file at `<memory>/daily/YYYY-MM-DD.md` with a start-of-day structure. If the file already exists, skip (idempotent)
-- Call `/groove-utilities-task-analyse` to get current task state
-- Do NOT archive tasks during start
+- 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

skills/groove/SKILL.md

@@ -5,7 +5,7 @@ license: MIT
 allowed-tools: Read Write Edit Glob Grep Bash(git:*) Bash(beans:*) Bash(gh:*) Bash(linear:*) Bash(npx:*) Bash(mkdir:*) AskUserQuestion
 metadata:
   author: andreadellacorte
-  version: "0.11.0"
+  version: "0.11.1"
 ---
 
 <!-- groove:managed — do not edit; changes will be overwritten by groove update -->