groove-work-audit
Installation
SKILL.md
groove-work-audit
Outcome
Blindspots and gaps are identified, actionable improvements are offered.
Acceptance Criteria
Findings are categorized by action:
- Fix Now: Trivial effort, fix immediately
- Needs Spec: Important, requires planning
- Create Issues: Large effort or nice-to-have
Constraints
- Sanitize topic (if provided) for safe use — strip path separators, special characters, and traversal patterns (
../) - Specs directory is always
.groove/memory/specs/ - Gather context: branch diff, relevant specs
- Run analysis in isolated context (use general-purpose agent)
- Fall back to direct review if subagent fails
- Present findings with severity and effort estimates
- Execute chosen action: fix directly, create spec via
/groove-work-spec <topic>, or create issues
Scope Options
- No args: Review current branch vs main
- Topic: Focus on specific area
Related skills
More from andreadellacorte/groove
groove
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
248groove-utilities-task-config
Configure task backend settings interactively.
227groove-utilities-check
Check if a newer version of groove is available on GitHub.
226groove-utilities-task-update
Update an existing task in the configured backend.
226groove-utilities-task-doctor
Check task backend health and connectivity.
225groove-admin-config
Create or update .groove/index.md config interactively. Run before groove install.
224