@smartsoft001-mobilems/claude-plugins 2.69.0 → 2.71.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smartsoft001-mobilems/claude-plugins",
-  "version": "2.69.0",
+  "version": "2.71.0",
   "publishConfig": {
     "access": "public"
   },

package/plugins/flow/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "flow",
   "description": "Development flow commands for Linear-driven development workflow",
-  "version": "2.69.0"
+  "version": "2.71.0"
 }

package/plugins/flow/commands/push.md

@@ -336,19 +336,76 @@ If user chooses not to verify, end the command here.
 
 **If workflow FAILED**:
 
-```markdown
-## ❌ CI Pipeline Failed
+1. **Get failed job logs**:
 
-**Workflow**: <workflow-name>
-**Run ID**: <run-id>
-**Conclusion**: failure
+   ```bash
+   gh run view <run-id> --log-failed 2>&1 | tail -100
+   ```
 
-### View logs
+2. **Revert Linear task to "To Do"**:
 
-Run `gh run view <run-id> --log-failed` to see error details.
+   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"
 
-Or visit: https://github.com/<owner>/<repo>/actions/runs/<run-id>
-```
+3. **Add error comment to Linear task**:
+
+   Create a comment on the **parent task** with CI error details:
+
+   ```markdown
+   ## ❌ CI Build Failed
+
+   ### Branch
+
+   `<branch-name>`
+
+   ### Workflow
+
+   **Name**: <workflow-name>
+   **Run ID**: <run-id>
+   **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
+
+   Task przywrócony do "To Do" z powodu błędu CI.
+
+   ---
+
+   _Raport wygenerowany przez Claude Code_
+   ```
+
+4. **Show error to user**:
+
+   ```markdown
+   ## ❌ CI Pipeline Failed
+
+   **Workflow**: <workflow-name>
+   **Run ID**: <run-id>
+   **Conclusion**: failure
+
+   ### Linear Task Status
+
+   ⚠️ Task [linearTaskId] przywrócony do "To Do"
+   ✅ Komentarz z błędem dodany do taska
+
+   ### View logs
+
+   Run `gh run view <run-id> --log-failed` to see error details.
+
+   Or visit: https://github.com/<owner>/<repo>/actions/runs/<run-id>
+
+   ### Następne kroki
+
+   1. Przeanalizuj błędy w CI
+   2. Napraw problemy lokalnie
+   3. Uruchom `/push-local` ponownie
+   ```
 
 Stop here if workflow failed.
 
@@ -485,7 +542,8 @@ Show complete summary:
 8. **Deployment verification is optional**: Always ask user before starting the 10-minute verification process
 9. **Read SITE_URL from .env.dev**: Use the SITE_URL variable from `.env.dev` file for QA verification
 10. **Version comparison**: Compare `package.json` version with `<meta name="app-version">` tag on QA site
-11. **Branch-specific post-push actions**:
+11. **Revert on CI failure**: If CI pipeline fails, move task back to "To Do" and add error comment
+12. **Branch-specific post-push actions**:
     - **`development` branch**: Offer deployment verification (CI monitoring + QA version check)
     - **Feature branch (e.g., `MOB-123`)**: Check/create PR to `development` when all subtasks are ready
 

package/plugins/flow-legacy/.claude-plugin/plugin.json

@@ -1,5 +1,5 @@
 {
   "name": "flow-legacy",
   "description": "Development flow commands for legacy Angular 14 projects with Linear-driven workflow",
-  "version": "2.69.0"
+  "version": "2.71.0"
 }

package/plugins/flow-legacy/commands/commit.md

@@ -90,16 +90,6 @@ Before creating the commit, **always** run the following commands:
    source ~/.nvm/nvm.sh && nvm use 18
    ```
 
-2. **Format the code**:
-
-   ```bash
-   npm run format
-   ```
-
-3. **Stage any formatting changes**:
-   - If `npm run format` modified any files, stage them with `git add`
-   - This ensures all committed code is properly formatted
-
 ### Step 5: Create Commit
 
 Execute the commit with the generated message:
@@ -159,4 +149,4 @@ For Linear task "ENG-123: Add dark mode toggle to settings":
 
 ---
 
-**Important**: Before committing, show the generated commit message to the user for approval.
+**Important**: Before committing, show the generated commit message to the user for approval.

package/plugins/flow-legacy/commands/push.md

@@ -337,19 +337,76 @@ If user chooses not to verify, end the command here.
 
 **If workflow FAILED**:
 
-```markdown
-## ❌ CI Pipeline Failed
+1. **Get failed job logs**:
 
-**Workflow**: <workflow-name>
-**Run ID**: <run-id>
-**Conclusion**: failure
+   ```bash
+   gh run view <run-id> --log-failed 2>&1 | tail -100
+   ```
 
-### View logs
+2. **Revert Linear task to "To Do"**:
 
-Run `gh run view <run-id> --log-failed` to see error details.
+   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"
 
-Or visit: https://github.com/<owner>/<repo>/actions/runs/<run-id>
-```
+3. **Add error comment to Linear task**:
+
+   Create a comment on the **parent task** with CI error details:
+
+   ```markdown
+   ## ❌ CI Build Failed
+
+   ### Branch
+
+   `<branch-name>`
+
+   ### Workflow
+
+   **Name**: <workflow-name>
+   **Run ID**: <run-id>
+   **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
+
+   Task przywrócony do "To Do" z powodu błędu CI.
+
+   ---
+
+   _Raport wygenerowany przez Claude Code (flow-legacy)_
+   ```
+
+4. **Show error to user**:
+
+   ```markdown
+   ## ❌ CI Pipeline Failed
+
+   **Workflow**: <workflow-name>
+   **Run ID**: <run-id>
+   **Conclusion**: failure
+
+   ### Linear Task Status
+
+   ⚠️ Task [linearTaskId] przywrócony do "To Do"
+   ✅ Komentarz z błędem dodany do taska
+
+   ### View logs
+
+   Run `gh run view <run-id> --log-failed` to see error details.
+
+   Or visit: https://github.com/<owner>/<repo>/actions/runs/<run-id>
+
+   ### Następne kroki
+
+   1. Przeanalizuj błędy w CI
+   2. Napraw problemy lokalnie
+   3. Uruchom `/push` ponownie
+   ```
 
 Stop here if workflow failed.
 
@@ -416,7 +473,8 @@ Angular 14 (legacy patterns)
 7. **Document incomplete subtasks**: Always explain WHY a subtask wasn't completed
 8. **Deployment verification is optional**: Always ask user before starting the verification process
 9. **Read SITE_URL from .env.dev**: Use the SITE_URL variable from `.env.dev` file for QA verification
-10. **Branch-specific post-push actions**:
+10. **Revert on CI failure**: If CI pipeline fails, move task back to "To Do" and add error comment
+11. **Branch-specific post-push actions**:
     - **`development` branch**: Offer deployment verification (CI monitoring + QA version check)
     - **Feature branch (e.g., `MOB-123`)**: Check/create PR to `development` when all subtasks are ready