task-valid-review

[Task Mgmt] Verification tool for validating task completion in Review section. Use when checking if tasks are actually done before moving from Review to Done. Verifies subtask completion, code/file changes, and task-work alignment. Optional but recommended for quality assurance. (user)

$ 설치

git clone https://github.com/CANTAGESTUDIO/CosmicAtlasPacker /tmp/CosmicAtlasPacker && cp -r /tmp/CosmicAtlasPacker/.claude/skills/task-valid-review ~/.claude/skills/CosmicAtlasPacker

// tip: Run this command in your terminal to install the skill


name: task-valid-review description: "[Task Mgmt] Verification tool for validating task completion in Review section. Use when checking if tasks are actually done before moving from Review to Done. Verifies subtask completion, code/file changes, and task-work alignment. Optional but recommended for quality assurance. (user)"

Task Valid Review

Verification skill for validating task completion. Use this when reviewing tasks in the Review section to check if work is actually complete before moving to Done.

When to Use

SituationUsage
Task is in Review sectionVerify before moving to Done
User wants to check completionRun validation checklist
Uncertain if work matches taskGenerate validation report

Note: This is a verification tool for the Review stage, not a mandatory gate. AI moves tasks to Review first, then this tool helps verify completion.

Verification Checklist

1. Subtask Completion Check

Check if all subtasks are completed.

Validation Steps:
1. Count total subtasks under parent task
2. Count completed subtasks (- [x])
3. If incomplete subtasks exist → List them
4. Determine if task is ready for Done

2. Code/File Change Verification

Check if actual changes exist for code-related tasks.

Task TypeExpected Evidence
New FeatureNew files created OR existing files modified
Bug FixCode changes in relevant files
RefactoringFile modifications detected
UI/UXView/Component files changed
Documentation.md files created/modified

Verification Method:

git status                    # Check current changes
git diff --stat HEAD~N        # Check recent commits

3. Task-Work Alignment Check

Check if completed work matches the task description.

CheckDescription
Title MatchWork addresses what the task title describes
Scope MatchAll aspects mentioned in subtasks are addressed
No Partial WorkNo "TODO" or "FIXME" left in new code
Build SuccessCode compiles without errors

Output Format

On Validation PASS:

## Task Validation: PASS ✅

**Task:** [Task Title]
**Subtasks:** 5/5 completed
**Files Changed:** 3 files (+120, -45 lines)
**Evidence:**
- Created: `Sources/Features/Login/LoginView.swift`
- Modified: `Sources/App/AppCoordinator.swift`

→ Ready to move from Review to Done

On Validation FAIL:

## Task Validation: FAIL ❌

**Task:** [Task Title]
**Reason:** [Specific failure reason]

**Issues Found:**
1. ❌ Subtasks incomplete: 2/5 completed
   - [ ] Add form validation logic
   - [ ] Handle error states
2. ❌ No file changes detected

**Recommended Actions:**
- Complete remaining subtasks
- Move back to Worker for more work

Exception Cases (No Code Changes Expected)

Task TypeValid Reason for No Code
Research/AnalysisOutput is documentation or notes
PlanningOutput is plan document
ReviewOutput is review comments
Documentation-onlyOnly .md files expected

Related Skills

SkillWhen to Use
task-moverMove task from Review to Done after verification
task-segmentationIf subtasks need more breakdown
task-addWhen discovering additional work needed
history-loggerAfter task moves to Done, log completion