بنقرة واحدة
groove-work-review
Evaluate output, identify lessons, decide accept/rework. Use after implementation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Evaluate output, identify lessons, decide accept/rework. Use after implementation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Groove engineering workflow system. Top-level entry point. Use groove-daily-*, groove-work-*, groove-utilities-*, groove-admin-* for all workflow and admin commands.
Install a rich Claude Code statusline into ~/.claude/hooks/ and ~/.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.
Set up task backend and configuration.
Install groove's Claude Code native shell hooks into .claude/settings.json. Enables deterministic session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.
Install groove's Cursor native hooks into .cursor/hooks.json. Enables compaction-safe re-priming, session-end reminders, git activity capture, automatic session-capture drafts, and managed-path protection.
Run all groove health checks: config, backends, companions, AGENTS.md.
| name | groove-work-review |
| description | Evaluate output, identify lessons, decide accept/rework. Use after implementation. |
| license | MIT |
| allowed-tools | Read Write Edit Glob Grep Bash(git:*) AskUserQuestion |
| metadata | {"author":"andreadellacorte"} |
The artifact is reviewed for correctness, quality, and fit to plan. Lessons are identified for the compound stage. A clear accept/rework decision is made with rationale. Review notes are captured in the task body.
/groove-work-compoundYYYY-MM-DD, ReviewBranch-diff analysis: determine the base branch (default: main; override with base: arg if provided). Run:
git log --oneline <base>...HEAD — list commits on this branchgit diff <base>...HEAD --stat — summarise changed filesgit diff <base>...HEAD — full diff (use as review input)
Use this diff as the primary artifact to evaluate. If no commits beyond base exist, review working-tree changes instead.Evaluate against plan and acceptance criteria — read the plan from the task body or spec file if available.
Categorise findings (use these exact labels):
State accept or rework decision with rationale.
Note lessons for /groove-work-compound.
Append review notes to the task body.
Create stage task via /groove-utilities-task-create if tasks.backend != none (title YYYY-MM-DD, Review).
tasks.backend from .groove/index.md to determine backend