You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**Agent push 403: switch gh auth to repo owner.** When the agent runs in an environment where multiple GitHub accounts are logged in (e.g. andreadellacorte-converge and andreadellacorte), `git push` may use the wrong credential and get 403. Run `gh auth switch --user <repo-owner>` (e.g. `andreadellacorte` for this repo); optionally run `gh auth setup-git` so Git uses the active gh account. Then push from the user’s side or re-run push.
6
+
3
7
## 2026-03-01
4
8
5
9
-**Test migrations through the system, not manually.** When developing groove itself, keep local `groove-version:` at the previous version, push the migration file, then run `groove update` to exercise it. Applying migration steps by hand before pushing means the migration is never tested through the system — the version already matches on the next `groove update` and the migration is silently skipped.
@@ -138,7 +134,7 @@ Both tools have spec and doc creation — this is the most direct overlap.
138
134
139
135
| Dimension | groove | bonfire |
140
136
|---|---|---|
141
-
| Upgrade command |`grooveupdate` — pulls latest via `npx skills add`, applies pending migrations | Not present — `npx skills add vieko/bonfire` re-installs; no migration runner |
137
+
| Upgrade command |`groove:update` — pulls latest via `npx skills add`, applies pending migrations | Not present — `npx skills add vieko/bonfire` re-installs; no migration runner |
142
138
| Migration system | Ordered runner: `migrations/index.md` table; filter `To > local AND To <= installed`; idempotent | Not present — backward-compat design; breaking config keys auto-detected on next run |
143
139
| Version tracking | Dual: skill `version:` in SKILL.md + user `groove-version:` in `.groove/index.md`| Skill `version:` in SKILL.md only |
144
140
| Breaking changes | Handled via migrations (v5.5.0 example: `linear: true/false` → `issues: true/false`) | Config keys auto-migrate on detection (e.g. `linear:` → `issues:` in v5.0.0) |
@@ -151,8 +147,8 @@ Both tools have spec and doc creation — this is the most direct overlap.
Copy file name to clipboardExpand all lines: .groove/memory/specs/groove-vs-groove.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ Synthesised from scope observations across all three comparisons:
24
24
-**Project-scoped, not global** — `.groove/` lives in the repo; PAI-style global installs (`~/.claude/`) are out of scope
25
25
-**Opinionated daily rhythm** — the start/end ceremony is a core differentiator; no other compared tool has it
26
26
-**Explicit 5-stage compound loop** — the most structured development workflow of any compared tool; "80% of value in plan and review" is baked in
27
-
-**Predictable explicit invocation** — `/groove<skill><command>` is more predictable than auto-discovery; keep it
27
+
-**Predictable explicit invocation** — `/groove:<skill>:<command>` is more predictable than auto-discovery; keep it
28
28
-**Backend-agnostic task abstraction** — beans/linear/github/none is unique; no other tool has an abstraction layer over task backends
29
29
30
30
---
@@ -60,7 +60,7 @@ Ordered by signal strength (how many comparisons surfaced it) and alignment with
60
60
61
61
- Bonfire's `/bonfire review` is the sharpest gap: branch-diff-based analysis, findings categorised as Fix Now / Needs Spec / Create Issues with effort estimates; no equivalent in groove
62
62
- Groove's `work review` is subjective (evaluate output against plan); it doesn't look at the actual diff
63
-
-**groove-scoped implementation**: Add a `grooveworkreview` step that runs `git diff <base>...HEAD` and `git log --oneline <base>..HEAD`; feeds into the review analysis; findings categorised by the same Fix Now / Needs Spec / Create Issues pattern. Fits naturally into the existing `work review` command; no new command needed.
63
+
-**groove-scoped implementation**: Add a `groove:work:review` step that runs `git diff <base>...HEAD` and `git log --oneline <base>..HEAD`; feeds into the review analysis; findings categorised by the same Fix Now / Needs Spec / Create Issues pattern. Fits naturally into the existing `work review` command; no new command needed.
64
64
65
65
**C. Session health check at end**
66
66
@@ -83,7 +83,7 @@ Ordered by signal strength (how many comparisons surfaced it) and alignment with
- Groove has no user-context layer that survives across sessions
86
-
-**groove-scoped implementation**: A single optional `.groove/IDENTITY.md` free-form file; `grooveprime` checks for it and includes it in conversation context output if present. No new config key; presence of file = enabled.
86
+
-**groove-scoped implementation**: A single optional `.groove/IDENTITY.md` free-form file; `groove:prime` checks for it and includes it in conversation context output if present. No new config key; presence of file = enabled.
87
87
88
88
**F. Multi-platform documentation**
89
89
@@ -129,6 +129,6 @@ groove is not: a personal AI OS (PAI), a plugin marketplace (night-market), or a
129
129
| v0.9.1 | Branch-diff analysis in `work review` (Fix Now / Needs Spec / Create Issues) | 1B |
130
130
| v0.9.2 | Session health check in `memory session end` (orphaned specs, long-running sessions) | 1C |
131
131
| v0.9.3 | Configurable `specs:` and `docs:` paths in `.groove/index.md`| 1D |
132
-
| v0.10.0 | TELOS-lite: `.groove/IDENTITY.md` surfaced by `grooveprime`| 2E |
132
+
| v0.10.0 | TELOS-lite: `.groove/IDENTITY.md` surfaced by `groove:prime`| 2E |
133
133
| v0.10.1 | Session rating signal → `learned/signals.md`| 2G |
134
134
| — | Multi-platform README docs | 2F (no version bump needed) |
Copy file name to clipboardExpand all lines: .groove/memory/specs/groove-vs-night-market.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@
36
36
| Dimension | groove | claude-night-market |
37
37
|---|---|---|
38
38
| Total commands |~26 across 5 sub-skills | 114 across 16 plugins |
39
-
| Invocation | Explicit only: `/groove<skill><command>`| Explicit (`/command`) OR auto-invoked when Claude matches task context to skill description |
39
+
| Invocation | Explicit only: `/groove:<skill>:<command>`| Explicit (`/command`) OR auto-invoked when Claude matches task context to skill description |
40
40
| Auto-discovery | Not present — user must know and type the command | Yes — `attune v1.4.0` enhanced auto-matching; Claude evaluates skill frontmatter |
41
41
| Keyboard shortcuts | Not present | Supported (e.g. resume screen with preview and rename shortcut) |
42
42
| Command scope | Compound: one entry point routes everything | Flat: each plugin adds its own namespace; no cross-plugin routing |
| Upgrade command |`/grooveupdate` — pulls latest via `npx skills add`, applies pending migrations |`/update-plugins` — recommends upgrades based on stability metrics; detects orphaned references |
64
+
| Upgrade command |`/groove:update` — pulls latest via `npx skills add`, applies pending migrations |`/update-plugins` — recommends upgrades based on stability metrics; detects orphaned references |
65
65
| Migration system | Ordered runner: `migrations/index.md` table; filter `To > local AND To <= installed`; idempotent per step | Not present — backward-compat design avoids breaking changes entirely |
66
66
| Version tracking | Dual: skill `version:` in SKILL.md + user `groove-version:` in `.groove/index.md`| Per-plugin version in `plugin.json`; stability metrics tracked per command (failure rate, usage freq) |
67
67
| Breaking changes | Handled via migrations (config key renames, dir moves, AGENTS.md rewrites) | Avoided by design; progressive loading preserves old configs |
68
68
| CI drift | Not present |`/update-ci` reconciles pre-commit hooks and GitHub Actions with code changes |
69
-
| Self-updating |`grooveupdate` re-reads `update.md` from disk after pull (bootstrapping fix) | Not described |
69
+
| Self-updating |`groove:update` re-reads `update.md` from disk after pull (bootstrapping fix) | Not described |
70
70
71
71
---
72
72
@@ -76,7 +76,7 @@
76
76
|---|---|---|
77
77
| Session files | Named markdown at `<memory>/sessions/<name>.md` with YAML frontmatter | Native Claude Code sessions + sanctum git workspace capture before resume |
78
78
| Auto-naming |`<branch>-YYYY-MM-DD-N` when name not provided | Explicit by convention: `debugging-auth-401`, `feature-payment-milestone-2`|
79
-
| Resume |`/groove memory session resume` — lists active sessions, user picks|`claude --resume [name]` or `claude --from-pr [number]` — PR-linked sessions |
| Learned memory |`.groove/memory/learned/<topic>.md` — cold-tier for workflow insights | Not present as explicit tier |
82
82
| Memory search | Not present — files are read manually | Hybrid: semantic (AI embedding) + lexical (keyword); auto-compaction on context fill |
@@ -105,7 +105,7 @@
105
105
| Dimension | groove | claude-night-market |
106
106
|---|---|---|
107
107
| AGENTS.md | Managed bootstrap: 2-line groove:prime stub + 2-line task stub; full context loaded on-demand | Full AGENTS.md standard support; CLAUDE.md → AGENTS.md migration supported |
108
-
| Context loading | On-demand: agent runs `/grooveprime` to load workflow context into conversation | Progressive Disclosure Architecture — skills auto-discover without loading all documents |
108
+
| Context loading | On-demand: agent runs `/groove:prime` to load workflow context into conversation | Progressive Disclosure Architecture — skills auto-discover without loading all documents |
109
109
| Hook system | Not present | PreToolUse hooks: imbue (TDD), conserve (permissions); can block, approve, or modify tool calls |
110
110
| Managed sections |`<!-- groove:managed -->` comment prevents agents editing `skills/` or `.agents/skills/`| Not needed — plugins installed to separate dir (`~/.claude/`) from user workspace |
111
111
| Allowed-tools | Declared per-skill in SKILL.md frontmatter | Declared per-plugin in `plugin.json`|
@@ -119,7 +119,7 @@
119
119
| Dimension | groove | claude-night-market |
120
120
|---|---|---|
121
121
| Config file |`.groove/index.md` YAML frontmatter — single source for all groove config |`.claude/settings.json` for hooks; `plugin.json` per plugin for plugin config |
122
-
| Config wizard |`/grooveconfig` — interactive, guided wizard with defaults | Not present |
122
+
| Config wizard |`/groove:config` — interactive, guided wizard with defaults | Not present |
| Cache |`.groove/.cache/` — always gitignored; `last-version-check` as plain text | Native Claude Code handles session state; no equivalent |
125
125
| Task backends | beans / linear / github / none — abstraction layer; CLI mapped in `references/backends.md`| GitHub Issues (minister plugin); no abstraction layer |
@@ -164,7 +164,7 @@ Things night-market does not have that groove should preserve and develop:
164
164
3.**Explicit 5-stage compound loop** — more opinionated and constraint-enforcing than attune's lifecycle; the "80% of value in plan and review" insight is baked into the skill.
165
165
4.**Learned memory tier** — `.groove/memory/learned/<topic>.md` as an explicit cold-tier for workflow insights with routing from both compound and session end; not present in night-market.
166
166
5.**Daily rituals with structured log roll-ups** — start/end with daily→weekly→monthly roll-up chain; no equivalent in night-market.
167
-
6.**Config wizard + version tracking** — `/grooveconfig` wizard and `groove-version:` migration gating is more robust than night-market's version management.
167
+
6.**Config wizard + version tracking** — `/groove:config` wizard and `groove-version:` migration gating is more robust than night-market's version management.
168
168
7.**groovebook (planned)** — a shared PR-based commons for cross-user workflow learnings; no equivalent exists.
0 commit comments