team-reviewlisted

# Code Review Skill ## Overview Code review skill for feature branches. Performs inline code analysis (compliance, bugs, history) with confidence scoring and filtering, optionally enriched with Context7 best-practice research. Supports PR integration for posting review comments. **Trigger**: `/team-review` ## When to Use Activate this skill when code needs quality check before PR/merge request. Not for: - Testing or functionality verification - Main/develop branch (must be on feature branch) - Single file reviews (use for branch-wide changes) ## Workflow **Phase tracking** — first action of the skill: call `TaskCreate` with these 7 items (status `pending`), then use `TaskUpdate` to set each phase `in_progress` at start and `completed` at end. On context compaction the task list remains visible — no risk of forgotten phases. 1. Step 1: Detection & Setup 2. Step 2: Mode Selection 3. Step 3: Gather Context 4. Step 4: Inline Review Analysis 5. Step 5: Confidence Scoring & Filtering 6. Step 6: Generate Feedback 7. Step 7: Output & PR Integration ### Step 1: Detection & Setup > **Todo**: call `TaskCreate` with the 7 phase items (see above). Mark Step 1 → `in_progress` via `TaskUpdate`. 0. **Team-mode gate.** Read `TEAM_MODE` via `shared/PROJECT-MODE.md` read pattern. If `"solo"` or absent → show AskUserQuestion (warn-only): ```yaml header: "Solo project" question: "This project is marked solo (team.mode). /team-review is meant for projects with multiple contr