@smartsoft001-mobilems/claude-plugins 2.71.0 → 2.73.0

package/plugins/flow-legacy/{commands/push.md → skills/push/SKILL.md}

@@ -1,7 +1,89 @@
-# Push Command
+---
+name: push
+description: Push local changes to remote repository, update Linear task status, monitor CI pipeline, verify QA deployment, and optionally create pull requests for feature branches. Uses Angular 14 legacy patterns.
+allowed-tools:
+  - Bash
+  - Read
+  - Glob
+  - Grep
+  - AskUserQuestion
+  - WebFetch
+  - TaskCreate
+  - TaskUpdate
+  - TaskList
+  - TaskGet
+  - mcp__linear-server__get_issue
+  - mcp__linear-server__list_issues
+  - mcp__linear-server__list_comments
+  - mcp__linear-server__create_comment
+  - mcp__linear-server__update_issue
+  - mcp__linear-server__list_issue_statuses
+---
+
+# Push Skill
 
 Push local changes to remote and optionally update Linear task status.
 
+## Execution Checklist
+
+Execute each step in order. Do not skip any step marked as MANDATORY.
+
+### Pre-Push
+
+- [ ] **1. Check git status** — verify branch, commits ahead, warn about uncommitted changes
+- [ ] **2. Get commits to push** — `git log origin/<branch>..HEAD --oneline`; exit if none
+- [ ] **3. Fetch Linear task** — get title, status, subtasks and their statuses via MCP
+- [ ] **4. Analyze subtasks** — classify completed vs incomplete, find reasons for incomplete ones
+- [ ] **5. MANDATORY: Show summary to user** — present commits + subtask status, ask about status change
+- [ ] **6. Update Linear status** — BEFORE push: set completed subtasks to "In Review", post summary comment in Polish
+- [ ] **7. MANDATORY: Write Linear comments in Polish** — all comments must be in Polish language
+
+### Push
+
+- [ ] **8. Push to remote** — `git push`; handle errors gracefully
+
+### Post-Push (branch-specific)
+
+#### If `development` branch:
+
+- [ ] **9a. Ask about deployment verification** — offer optional CI monitoring + QA check
+- [ ] **10a. Monitor CI pipeline** — poll `gh run view` every 30s until completion
+- [ ] **11a. Handle CI failure** — revert task to "To Do", post error comment to Linear
+- [ ] **12a. Verify package.json update** — `git pull`, compare versions
+- [ ] **13a. Verify QA deployment** — wait 5 min, check `<meta name="app-version">` matches
+
+#### If feature branch:
+
+- [ ] **9b. Check for existing PR** — `gh pr list --head <branch> --base development`
+- [ ] **10b. Ask about PR creation** — if no PR exists and subtasks are ready
+- [ ] **11b. Create PR** — `gh pr create` with structured summary including Angular 14 tech stack
+
+### Final
+
+- [ ] **12. Show final status** — complete summary of all actions taken
+
+### Task Progress Tracking
+
+**MANDATORY**: Use Claude Code's built-in task tracking to provide real-time progress visibility.
+
+**At skill start**: Create tasks for each checklist step using `TaskCreate`:
+
+```
+TaskCreate({
+  subject: "Check git status",
+  description: "Verify branch, commits ahead, warn about uncommitted changes",
+  activeForm: "Checking git status"
+})
+```
+
+**During execution**:
+
+- Before starting a step → `TaskUpdate({ taskId, status: "in_progress" })`
+- After completing a step → `TaskUpdate({ taskId, status: "completed" })`
+- For branch-specific steps, only create tasks for the applicable branch path (development OR feature)
+
+**Before user decisions**: Use `TaskList` to show progress overview before asking user about status changes or PR creation.
+
 ## Usage
 
 ```
@@ -346,6 +428,7 @@ If user chooses not to verify, end the command here.
 2. **Revert Linear task to "To Do"**:
 
    If Linear task was provided and status was changed to "In Review":
+
    - Move the parent task back to "To Do" status
    - For tasks with subtasks: Move all subtasks that were changed to "In Review" back to "To Do"
 
@@ -367,9 +450,10 @@ If user chooses not to verify, end the command here.
    **URL**: https://github.com/<owner>/<repo>/actions/runs/<run-id>
 
    ### Error Details
-
    ```
+
    <last 50-100 lines of error logs from gh run view --log-failed>
+
    ```
 
    ### Status