@smartsoft001-mobilems/claude-plugins 2.67.0 → 2.69.0

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

@@ -0,0 +1,470 @@
+# Push Command
+
+Push local changes to remote and optionally update Linear task status.
+
+## Usage
+
+```
+/push [linearTaskId]
+```
+
+## Parameters
+
+- `linearTaskId` - Linear task ID (e.g., MOB-123)
+
+## Instructions
+
+You are tasked with pushing local changes to the remote repository, summarizing what was done, and optionally moving the Linear task to "In Review".
+
+### Step 1: Check Git Status
+
+Run `git status` to verify:
+
+- Current branch name
+- Number of commits ahead of remote
+- Any uncommitted changes (warn user if present)
+
+If there are uncommitted changes, warn the user and ask if they want to proceed or commit first.
+
+### Step 2: Get Commits to Push
+
+Run `git log origin/<branch>..HEAD --oneline` to get the list of commits that will be pushed.
+
+If no commits to push, inform the user and exit.
+
+### Step 3: Fetch Linear Task Details (if linearTaskId provided)
+
+If `linearTaskId` was provided, use MCP Linear server to fetch:
+
+- Task title
+- Current status
+- Subtasks (if any) and their statuses
+- Comments on subtasks (to find reasons for incomplete items)
+
+### Step 4: Analyze Subtasks Status
+
+For each subtask, determine:
+
+1. **Completed subtasks**: Status is "Done", "In Review", or has implementation completed
+2. **Incomplete subtasks**: Status is "To Do", "Blocked", or was not implemented
+
+For incomplete subtasks, find the reason by:
+
+- Reading comments on the subtask (look for "Analiza problemu", "Blocker", "Status: Blocked")
+- Checking if it was marked as backend issue, external dependency, etc.
+
+Build a summary of incomplete items with reasons.
+
+### Step 5: Show Summary and Ask About Status Update
+
+Show summary of what will be pushed and ask user:
+
+```markdown
+## Podsumowanie
+
+### Commity do wysłania (X)
+
+| Commit  | Opis                       |
+| ------- | -------------------------- |
+| abc1234 | feat(scope): description 1 |
+| def5678 | fix(scope): description 2  |
+
+### Podzadania
+
+#### Zrealizowane
+
+- ✅ MOB-549: Naprawić szerokość logo
+- ✅ MOB-550: Usunąć zdublowane zdjęcia
+
+#### Niezrealizowane
+
+- ⚠️ MOB-554: Obsłużyć zdjęcia PNG → Problem backendu
+
+---
+
+**Task**: [linearTaskId] - [Task Title]
+**Aktualny status**: [Current Status]
+
+Czy przenieść task do "In Review" i wysłać zmiany?
+```
+
+Use `AskUserQuestion` tool with options:
+
+- "Tak, przenieś do In Review i wyślij" (Recommended)
+- "Tylko wyślij, bez zmiany statusu"
+- "Anuluj"
+
+### Step 6: Update Linear Status (if confirmed)
+
+**BEFORE pushing**, if user confirmed status change:
+
+1. **For tasks with subtasks**: Update all completed subtasks to "In Review"
+2. **For tasks without subtasks**: Update the task itself to "In Review"
+
+Create a comment on the **parent task** summarizing:
+
+```markdown
+## Podsumowanie Implementacji
+
+### Branch
+
+`<branch-name>`
+
+### Zrealizowane Podzadania
+
+| Podzadanie | Tytuł                     | Status          |
+| ---------- | ------------------------- | --------------- |
+| MOB-549    | Naprawić szerokość logo   | ✅ Zrealizowane |
+| MOB-550    | Usunąć zdublowane zdjęcia | ✅ Zrealizowane |
+
+### Niezrealizowane Podzadania
+
+| Podzadanie | Tytuł                | Powód                                                   |
+| ---------- | -------------------- | ------------------------------------------------------- |
+| MOB-554    | Obsłużyć zdjęcia PNG | ⚠️ Problem backendu - wymaga naprawy po stronie serwera |
+
+### Commity
+
+| Commit  | Opis                       |
+| ------- | -------------------------- |
+| abc1234 | feat(scope): description 1 |
+| def5678 | fix(scope): description 2  |
+
+### Angular Version
+
+Angular 14 (legacy patterns)
+
+### Status
+
+Task przeniesiony do "In Review".
+
+---
+
+_Raport wygenerowany przez Claude Code (flow-legacy)_
+```
+
+### Step 7: Push to Remote
+
+Execute `git push` to push the commits to the remote repository.
+
+If push fails:
+
+- Show the error message
+- Suggest possible solutions (pull first, force push if appropriate, etc.)
+- Note: Linear status was already updated, may need to revert if push ultimately fails
+
+### Step 8: Final Confirmation
+
+Show final status to user:
+
+```markdown
+## Gotowe
+
+✅ Linear task [linearTaskId] przeniesiony do "In Review"
+✅ Zmiany wysłane do `origin/<branch-name>`
+
+### Następne kroki
+
+- Oczekiwanie na code review
+```
+
+### Step 9: Branch-Specific Post-Push Actions
+
+After successful push, determine the next action based on the current branch:
+
+1. **If branch is `development`**: Proceed to **Step 10** (Deployment Verification)
+2. **If branch is a feature branch** (matches Linear issue ID pattern like `MOB-123`, `mob-123`, etc.): Proceed to **Step 9a** (PR Workflow)
+
+#### Step 9a: Feature Branch - Check/Create Pull Request
+
+**Applicable only when on a feature branch (not `development`).**
+
+1. **Check if all subtasks are completed**:
+
+   Review the subtask analysis from Step 4. Consider a task "ready for PR" if:
+
+   - All subtasks are in "Done" or "In Review" status, OR
+   - Incomplete subtasks have documented reasons (backend issue, external dependency, etc.)
+
+2. **Check if PR already exists**:
+
+   ```bash
+   gh pr list --head <branch-name> --base development --json number,title,state,url
+   ```
+
+3. **If PR exists**:
+
+   ```markdown
+   ## Pull Request Already Exists
+
+   **PR**: #<number> - <title>
+   **Status**: <state>
+   **URL**: <url>
+
+   No action needed - PR already created.
+   ```
+
+4. **If PR does NOT exist**, ask user:
+
+   ```markdown
+   ## Create Pull Request?
+
+   Branch `<branch-name>` has no open PR to `development`.
+
+   ### Subtasks Status
+
+   - ✅ Completed: X
+   - ⚠️ Incomplete: Y (with documented reasons)
+
+   Do you want to create a Pull Request?
+   ```
+
+   Use `AskUserQuestion` tool with options:
+
+   - "Tak, utwórz PR do development" (Recommended)
+   - "Nie, zakończ bez PR"
+
+5. **If user confirms PR creation**:
+
+   Create PR using `gh pr create`:
+
+   ```bash
+   gh pr create --base development --head <branch-name> --title "<Linear-ID>: <Task Title>" --body "$(cat <<'EOF'
+   ## Summary
+
+   Implementation for [<Linear-ID>](https://linear.app/issue/<Linear-ID>)
+
+   ### Technology Stack
+
+   - Angular 14 (legacy patterns)
+   - Nx 14 with @nrwl/* packages
+
+   ### Completed Subtasks
+
+   - ✅ <subtask-id>: <title>
+   - ✅ <subtask-id>: <title>
+
+   ### Incomplete Subtasks (with reasons)
+
+   - ⚠️ <subtask-id>: <title> → <reason>
+
+   ### Commits
+
+   | Commit | Description |
+   |--------|-------------|
+   | abc123 | feat: ... |
+
+   ---
+
+   🤖 Generated with [Claude Code](https://claude.com/claude-code) (flow-legacy)
+   EOF
+   )"
+   ```
+
+6. **Show PR creation result**:
+
+   ```markdown
+   ## ✅ Pull Request Created
+
+   **PR**: #<number> - <title>
+   **URL**: <url>
+   **Base**: development
+   **Head**: <branch-name>
+
+   ### Następne kroki
+
+   - Oczekiwanie na code review
+   - Po zatwierdzeniu: merge do development
+   ```
+
+   **End the command here for feature branches.**
+
+### Step 10: Ask About Deployment Verification (development branch only)
+
+**Applicable only when on `development` branch.**
+
+After successful push, ask the user if they want to verify deployment:
+
+```markdown
+## Deployment Verification
+
+Do you want to verify the deployment on QA environment?
+
+Verification process:
+
+1. Monitor GitHub Actions CI pipeline until completion
+2. Git pull and check if package.json was updated
+3. Wait 5 minutes for deployment
+4. Verify app version on QA site
+```
+
+Use `AskUserQuestion` tool with options:
+
+- "Yes, verify deployment" (Recommended)
+- "No, finish now"
+
+If user chooses not to verify, end the command here.
+
+### Step 11: Monitor CI Pipeline via GitHub Actions
+
+**Do NOT wait a fixed time.** Instead, actively monitor GitHub Actions workflows using `gh` CLI.
+
+1. **Get the latest workflow run for the current branch**:
+
+   ```bash
+   gh run list --branch <branch-name> --limit 1 --json databaseId,status,conclusion,workflowName
+   ```
+
+2. **Poll workflow status** every 30 seconds until it completes:
+
+   ```bash
+   gh run view <run-id> --json status,conclusion
+   ```
+
+3. **Show progress to user**:
+
+   ```markdown
+   ## CI/CD Pipeline Monitoring
+
+   🔄 Monitoring GitHub Actions workflow...
+
+   **Workflow**: <workflow-name>
+   **Run ID**: <run-id>
+   **Status**: in_progress | queued | completed
+   ```
+
+4. **Check workflow result**:
+
+**If workflow FAILED**:
+
+```markdown
+## ❌ CI Pipeline Failed
+
+**Workflow**: <workflow-name>
+**Run ID**: <run-id>
+**Conclusion**: failure
+
+### 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>
+```
+
+Stop here if workflow failed.
+
+**If workflow SUCCEEDED**, run:
+
+```bash
+git fetch origin
+git pull origin <branch-name>
+```
+
+Check if `package.json` version has changed and proceed to Step 12.
+
+### Step 12: Verify Deployment on QA (App Version Check)
+
+Wait 5 minutes for deployment to complete:
+
+```markdown
+## QA Deployment Verification
+
+⏳ Waiting 5 minutes for QA deployment...
+```
+
+Use `sleep 300` or equivalent to wait.
+
+After waiting, read SITE_URL from `.env.dev` file and fetch the page to verify app version.
+
+### Step 13: Final Deployment Status
+
+Show complete summary:
+
+```markdown
+## Complete Process Summary
+
+### Git
+
+✅ Changes pushed to `origin/<branch-name>`
+
+### Linear
+
+✅ Task [linearTaskId] moved to "In Review"
+
+### CI/CD Pipeline
+
+✅ Package.json updated to version X.X.X
+
+### QA Deployment
+
+✅ Application deployed to <SITE_URL>
+✅ Version: X.X.X
+
+### Technology
+
+Angular 14 (legacy patterns)
+```
+
+## Guidelines
+
+1. **Write comments in Polish**: All Linear comments must be written in Polish
+2. **Always confirm before status change**: Never change Linear status without user confirmation
+3. **Update Linear BEFORE push**: Status change happens before git push
+4. **Handle errors gracefully**: If push fails after status update, inform user
+5. **Warn about uncommitted changes**: Don't push if there are uncommitted changes without user acknowledgment
+6. **Show clear summaries**: Always show what commits will be pushed and subtask status
+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**:
+    - **`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
+
+## Error Handling
+
+### Push Rejected (non-fast-forward)
+
+```markdown
+## Push Failed
+
+**Error**: Updates were rejected because the remote contains work that you do not have locally.
+
+**Uwaga**: Status w Linear został już zaktualizowany do "In Review".
+
+### Options
+
+1. `git pull --rebase` - Pull remote changes and rebase your commits on top
+2. `git pull` - Pull remote changes and merge
+3. `git push --force` - Force push (⚠️ overwrites remote changes)
+
+Which option do you want to use?
+```
+
+### No Commits to Push
+
+```markdown
+## Nothing to Push
+
+Your branch is up to date with `origin/<branch-name>`.
+
+No commits to push.
+```
+
+### Uncommitted Changes Present
+
+```markdown
+## Warning: Uncommitted Changes
+
+You have uncommitted changes in your working directory:
+
+- modified: path/to/file1.ts
+- modified: path/to/file2.ts
+
+### Options
+
+1. Commit changes first (`/commit`)
+2. Stash changes and push
+3. Proceed anyway (push existing commits only)
+
+What would you like to do?
+```

package/plugins/flow-legacy/skills/a11y-audit/SKILL.md

@@ -0,0 +1,214 @@
+---
+name: a11y-audit
+description: Run accessibility audits on web pages. Ensures dev server is running, navigates to pages, captures accessibility snapshots, and runs axe-core tests.
+allowed-tools:
+  - Bash
+  - Read
+  - Glob
+  - mcp__playwright__browser_navigate
+  - mcp__playwright__browser_snapshot
+  - mcp__playwright__browser_evaluate
+  - mcp__playwright__browser_close
+---
+
+# Accessibility Audit Skill
+
+Run accessibility audits on web pages using Playwright and axe-core. Automatically ensures the development server is running before auditing.
+
+## Capabilities
+
+1. **Server Management**: Check if dev server is running, start if needed
+2. **Page Navigation**: Navigate to specified URLs using Playwright
+3. **Accessibility Snapshot**: Capture accessibility tree for analysis
+4. **Axe-core Testing**: Run automated accessibility tests
+
+## Server Management
+
+### Read Port Configuration
+
+```bash
+# Default port location (Nx 14 / Angular 14 project)
+grep -o '"port":[^,}]*' apps/web/project.json | head -1
+# Default: 4200
+```
+
+### Check if Server is Running
+
+```bash
+lsof -i :4200 -t
+```
+
+- If returns PID -> server is running
+- If returns nothing -> server needs to be started
+
+### Start Server if Needed
+
+```bash
+# Start in background (Nx 14 / @nrwl)
+npm start &
+
+# Wait for server to be ready
+for i in {1..15}; do
+  curl -s http://localhost:4200 > /dev/null && break
+  sleep 2
+done
+```
+
+## Audit Process
+
+### 1. Ensure Server is Running
+
+Before any audit:
+
+1. Read port from `apps/web/project.json` (default: 4200)
+2. Check if port is occupied: `lsof -i :PORT -t`
+3. If not running: `npm start &` and wait ~15 seconds
+
+### 2. Navigate to Page
+
+Use `mcp__playwright__browser_navigate` to open the target URL.
+
+```
+URL format: http://localhost:{port}/{path}
+```
+
+### 3. Capture Accessibility Snapshot
+
+Use `mcp__playwright__browser_snapshot` to get the accessibility tree.
+
+This provides:
+
+- Element roles and names
+- ARIA attributes
+- Focus states
+- Interactive element information
+
+### 4. Run Axe-core Audit
+
+Use `mcp__playwright__browser_evaluate` to inject and run axe-core:
+
+```javascript
+// Example evaluation code
+async () => {
+  // Load axe-core from CDN
+  const script = document.createElement('script');
+  script.src =
+    'https://cdnjs.cloudflare.com/ajax/libs/axe-core/4.8.2/axe.min.js';
+  document.head.appendChild(script);
+
+  await new Promise((resolve) => (script.onload = resolve));
+
+  // Run audit
+  const results = await axe.run();
+  return {
+    violations: results.violations,
+    passes: results.passes.length,
+    incomplete: results.incomplete,
+  };
+};
+```
+
+## Usage Examples
+
+### Full Page Audit
+
+```
+Input: { path: "/articles" }
+
+Process:
+1. Check server running on port 4200
+2. Start if needed, wait for ready
+3. Navigate to http://localhost:4200/articles
+4. Capture accessibility snapshot
+5. Run axe-core audit
+6. Return violations and recommendations
+
+Output:
+{
+  "url": "http://localhost:4200/articles",
+  "snapshot": { ... accessibility tree ... },
+  "violations": [
+    {
+      "id": "image-alt",
+      "impact": "critical",
+      "description": "Images must have alternate text",
+      "nodes": [...]
+    }
+  ],
+  "passes": 45,
+  "incomplete": 2
+}
+```
+
+### Quick Check
+
+```
+Input: { path: "/", snapshotOnly: true }
+
+Output:
+{
+  "url": "http://localhost:4200/",
+  "snapshot": { ... accessibility tree ... }
+}
+```
+
+## Report Format
+
+When generating reports, use this structure:
+
+```markdown
+## Accessibility Audit Report
+
+**Page**: [URL]
+**Date**: [Date]
+**Standard**: WCAG 2.1 Level AA
+
+### Critical Issues (Must Fix)
+
+| Issue       | Elements | WCAG  | Fix                      |
+| ----------- | -------- | ----- | ------------------------ |
+| Missing alt | 3 images | 1.1.1 | Add descriptive alt text |
+
+### Serious Issues (Should Fix)
+
+| Issue        | Elements   | WCAG  | Fix              |
+| ------------ | ---------- | ----- | ---------------- |
+| Low contrast | 2 elements | 1.4.3 | Use darker color |
+
+### Passed Checks
+
+- [x] Page has lang attribute
+- [x] Headings in correct order
+- [x] Form inputs have labels
+
+### Summary
+
+- Violations: X critical, Y serious, Z minor
+- Passed: N checks
+```
+
+## Error Handling
+
+### Server Won't Start
+
+If server fails to start after 30 seconds:
+
+1. Check for port conflicts
+2. Check npm logs for errors
+3. Report error and skip audit
+
+### Axe-core Load Fails
+
+If axe-core fails to load:
+
+1. Check network connectivity
+2. Try alternative CDN
+3. Fall back to snapshot-only audit
+
+### Navigation Fails
+
+If page doesn't load:
+
+1. Verify URL is correct
+2. Check for JavaScript errors
+3. Report partial results