Great Groove Migration

[lvndry]

This PR migrates the old workflow system to the new Groove-based automation model.

• Replaces WORKFLOW.md files with GROOVE.md-based grooves
• Introduces groove CLI commands and core groove runtime
• Updates docs and skills to reflect grooves instead of workflows

Please review groove definitions, CLI help, and docs for consistency.

[gemini-code-assist]

Summary of Changes

Hello @lvndry, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request undertakes a significant refactoring effort to transition the application's automation system from a 'workflow' paradigm to a new 'Groove-based' model. This change is comprehensive, impacting all layers from core services and CLI commands to file structures and user documentation, ensuring a consistent and unified experience under the new terminology.

Highlights

• Terminology Migration: The core automation concept has been renamed from 'Workflows' to 'Grooves' across the entire application, including code, documentation, and user-facing CLI commands.
• File Structure and Naming Convention Update: All WORKFLOW.md files and their containing workflows/ directories have been renamed to GROOVE.md and grooves/ respectively, standardizing the new naming convention.
• CLI Command Refactoring: All jazz workflow CLI commands have been updated to jazz groove, ensuring consistency with the new 'Groove-based automation model'.
• Core Service Rearchitecture: The underlying services responsible for managing, scheduling, and tracking automated tasks (e.g., workflow-service, scheduler-service, run-history, catch-up logic) have been refactored and renamed to align with the 'Groove' terminology.
• Comprehensive Documentation Alignment: All relevant documentation, including the README.md, conceptual guides, use cases, and CLI references, has been thoroughly updated to reflect the new 'Groove' terminology and file paths.

Changelog

• README.md
  • Updated feature descriptions, CLI command examples, and file references from 'workflow' to 'groove'.
• docs/concepts/agents.md
  • Replaced 'workflows' with 'grooves' in the description of agent routing capabilities.
• docs/concepts/grooves.md
  • Renamed from docs/concepts/workflows.md.
  • All content, including headings, descriptions, file paths, CLI commands, and conceptual explanations, updated to use 'groove' terminology.
  • Updated frontmatter fields and troubleshooting sections to reflect 'groove' naming.
• docs/concepts/index.md
  • Updated links and descriptions to refer to 'Grooves' instead of 'Workflows'.
• docs/concepts/scheduling.md
  • Renamed the documentation title and updated all content, examples, and FAQs to use 'groove' terminology.
  • Updated CLI commands and related documentation links.
• docs/concepts/skills.md
  • Updated the create-workflow skill to create-groove.
• docs/guide/use-cases/investment.md
  • Updated use case examples to refer to 'grooves' and GROOVE.md files.
• docs/guide/use-cases/meetings.md
  • Updated use case examples to refer to 'grooves' and GROOVE.md files.
• docs/index.md
  • Updated the main documentation index to link to 'Grooves'.
• docs/reference/cli.md
  • Updated CLI reference documentation to reflect jazz groove commands instead of jazz workflow.
• grooves/email-cleanup/GROOVE.md
  • Renamed from workflows/email-cleanup/WORKFLOW.md.
• grooves/market-analysis/GROOVE.md
  • Renamed from workflows/market-analysis/WORKFLOW.md.
• grooves/tech-digest/GROOVE.md
  • Renamed from workflows/tech-digest/WORKFLOW.md.
• grooves/weather-briefing/GROOVE.md
  • Renamed from workflows/weather-briefing/WORKFLOW.md.
• package.json
  • Added 'groove' and 'grooves' to keywords.
  • Updated the files array to include grooves/ instead of workflows/.
• skills/create-groove/SKILL.md
  • Renamed from skills/create-workflow/SKILL.md.
  • Updated skill name, description, instructions, and examples to use 'groove' terminology.
• skills/create-system-routine/SKILL.md
  • Minor terminology update from 'Workflows' to 'Grooves' in the description.
• skills/skill-creator/SKILL.md
  • Minor formatting adjustments (added blank lines for readability).
• src/app-layer.ts
  • Refactored imports and service layers to use core/grooves components instead of core/workflows.
  • Updated comments to refer to 'groove' for catch-up and session logs.
• src/cli/cli-app.ts
  • Updated CLI command registration to use groove commands and removed workflow commands.
  • Updated command descriptions from 'workflow' to 'groove'.
• src/cli/commands/groove.ts
  • Renamed from src/cli/commands/workflow.ts.
  • Performed a full find-and-replace of 'workflow' with 'groove' in code, types, and user messages for CLI commands.
• src/core/README.md
  • Updated an example path from agent/workflows/my-workflow.ts to grooves/my-groove/GROOVE.md.
• src/core/agent/tools/base-tool.ts
  • Updated comments to refer to 'grooves' for auto-approval risk levels.
• src/core/agent/types.ts
  • Updated comments to refer to 'grooves' for auto-approve policy.
• src/core/grooves/catch-up.test.ts
  • Renamed from src/core/workflows/catch-up.test.ts.
  • Updated test file content to use 'groove' terminology.
• src/core/grooves/catch-up.ts
  • Renamed from src/core/workflows/catch-up.ts.
  • Refactored all logic, types, and messages to use 'groove' terminology for catch-up functionality.
• src/core/grooves/groove-service.test.ts
  • Added new test file for GrooveService functionality, including metadata parsing and priority.
• src/core/grooves/groove-service.ts
  • Added new core service file defining GrooveMetadata, GrooveContent, and GrooveService for managing groove definitions.
• src/core/grooves/index.ts
  • Renamed from src/core/workflows/index.ts.
  • Updated module index and exports to reflect the new grooves components.
• src/core/grooves/run-history.test.ts
  • Renamed from src/core/workflows/run-history.test.ts.
  • Updated test file content to use 'groove' terminology.
• src/core/grooves/run-history.ts
  • Renamed from src/core/workflows/run-history.ts.
  • Refactored run history management to use 'groove' terminology and GrooveRunRecord.
• src/core/grooves/scheduler-service.test.ts
  • Renamed from src/core/workflows/scheduler-service.test.ts.
  • Updated test file content to use 'groove' terminology.
• src/core/grooves/scheduler-service.ts
  • Renamed from src/core/workflows/scheduler-service.ts.
  • Refactored the scheduler service to manage 'grooves' instead of 'workflows', including plist/crontab generation.
• src/core/grooves/utils.test.ts
  • Added new test file for groove utility functions.
• src/core/grooves/utils.ts
  • Added new utility file for grouping and formatting groove metadata.
• src/core/interfaces/chat-service.ts
  • Updated dependencies to use GrooveService instead of WorkflowService.
• src/core/interfaces/tool-registry.ts
  • Updated comments to refer to 'grooves' for tool risk levels.
• src/core/presentation/headless-presentation-service.ts
  • Updated comments to refer to 'groove runs' and 'groove catch-up'.
• src/core/utils/runtime-detection.ts
  • Updated functions and paths to detect grooves directories instead of workflows.
• src/core/workflows/workflow-service.test.ts
  • Removed.
• src/core/workflows/workflow-service.ts
  • Removed.
• src/core/workflows/workflow-utils.test.ts
  • Removed.
• src/core/workflows/workflow-utils.ts
  • Removed.
• src/services/chat-service.ts
  • Updated dependencies to use GrooveService instead of WorkflowService.
• src/services/chat/commands/constants.ts
  • Updated chat command description for /grooves.
• src/services/chat/commands/handler.ts
  • Refactored handleWorkflowsCommand to handleGroovesCommand and updated its logic and messages to use 'groove' terminology.
• src/services/chat/commands/parser.test.ts
  • Updated tests to parse /grooves command instead of /workflows.
• src/services/chat/commands/parser.ts
  • Updated command parsing logic to recognize /grooves instead of /workflows.
• src/services/chat/commands/types.ts
  • Updated CommandType to include 'grooves' instead of 'workflows'.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request renames the concept of 'workflows' to 'grooves' throughout the codebase and documentation. This change affects file paths (e.g., workflows/ directories become grooves/), file names (e.g., WORKFLOW.md becomes GROOVE.md), and all related code, CLI commands, and documentation. The WorkflowService is replaced by GrooveService, and all associated types, functions, and tests are updated to reflect the new 'groove' terminology. Additionally, minor formatting adjustments were made in the documentation, such as adding blank lines for readability and removing a duplicate 'Related Documentation' header, as noted in the review comments.

[gemini-code-assist]

This ## Related Documentation header appears to be a duplicate. You can likely remove it to clean up the document structure.

[gemini-code-assist]

This indented code fence seems to be a typo and is likely closing the markdown code block prematurely. You may want to remove this line.