Skip to content

[tooling] Rename review skills to deep-review-lite and deep-review-pro #435

@hubertgajewski

Description

@hubertgajewski

User Story

As a code-review workflow user, I want the legacy deep-review skill preserved under the clearer deep-review-lite name and the new orchestrator renamed from deep-review-next to deep-review-pro, so that both workflows remain available with names that communicate their scope.

Context

The new orchestrator currently ships under the provisional name deep-review-next while the legacy deep-review skill remains available. Instead of replacing the legacy workflow, keep it as the lightweight/manual review path and give the orchestrator a stable pro workflow name.

This story is gated on S7 closing as PASS.

Acceptance Criteria

  • Given S7 closed with PASS verdict, when S8 lands, then .claude/skills/deep-review/ is renamed to .claude/skills/deep-review-lite/ and .claude/skills/deep-review-next/ is renamed to .claude/skills/deep-review-pro/.
  • Given the rename PR, when I invoke deep-review-lite, then it runs the preserved legacy review workflow.
  • Given the rename PR, when I invoke deep-review-pro, then it dispatches the new agent stack (security, simplification, code, architecture, TS, Python, QA, unit-test, CI, docs, project-checklist).
  • Given the rename PR, when I check CLAUDE.md, README.md, and related Codex wrapper references, then all references distinguish deep-review-lite from deep-review-pro and no longer describe deep-review-next as the stable workflow name.
  • Given any problem after the rename, when I git revert the S8 commit, then both skills return to their pre-rename paths with no manual recovery.

Implementation Hint

Single PR:

  1. git mv .claude/skills/deep-review/ .claude/skills/deep-review-lite/
  2. git mv .claude/skills/deep-review-next/ .claude/skills/deep-review-pro/
  3. Update CLAUDE.md review-before-commit references so they name the intended default workflow explicitly.
  4. Update README.md, .agents/skills/ symlinks, .codex/agents/ wrappers, and any other references that mention deep-review or deep-review-next.

Definition of Done

  • Single atomic PR; both skill directories renamed in the same commit. Verified in PR #435 Rename review skills to lite and pro #531 commit 4ea5fac, which performs both directory renames together.
  • gh pr checkout on the S8 PR works; deep-review-lite invokes the preserved legacy workflow. Verified after PR #435 Rename review skills to lite and pro #531 checkout: .agents/skills/deep-review-lite/SKILL.md resolves to .claude/skills/deep-review-lite/SKILL.md, preserving the legacy checklist workflow.
  • gh pr checkout on the S8 PR works; deep-review-pro invokes the new orchestrator. Verified after PR #435 Rename review skills to lite and pro #531 checkout: .agents/skills/deep-review-pro/SKILL.md resolves to .claude/skills/deep-review-pro/SKILL.md, which dispatches the specialist review stack.
  • git revert of the S8 commit on a test branch restores the previous skill paths cleanly. Verified with the non-mutating reverse-diff equivalent because the repository hook blocked literal git revert: HEAD^ contains the previous deep-review and deep-review-next paths and no deep-review-lite or deep-review-pro paths.
  • CLAUDE.md, README.md, .agents/skills/, and .codex/agents/ are consistent with the new names. Verified by stale-reference rg scans, Prettier check, JSON validation, and symlink target checks.
  • Estimate = 1 set in Project #1. Verified on the [tooling] Rename review skills to deep-review-lite and deep-review-pro #435 project item.
  • Actual hours recorded in Project #1. Recorded 0.23 hours, derived from the active commit span on 2026-05-10 from 10:11:24 to 10:25:22 Europe/Warsaw.

Metadata

Metadata

Labels

enhancementNew feature or requesttoolingDeveloper tooling, scripts, and IDE configuration

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions