@smartsoft001-mobilems/claude-plugins 2.77.0 → 2.78.0

package/plugins/flow-external/skills/plan/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: plan
+description: Create implementation plan and save to Linear. Analyzes codebase, understands task requirements, and generates structured plan.
+allowed-tools:
+  - Bash
+  - Read
+  - Glob
+  - Grep
+  - AskUserQuestion
+  - mcp__linear-server__get_issue
+  - mcp__linear-server__list_issues
+  - mcp__linear-server__list_comments
+  - mcp__linear-server__create_comment
+  - mcp__linear-server__create_issue
+  - mcp__linear-server__update_issue
+---
+
+# Plan Skill
+
+Create a structured implementation plan for a Linear task and save it as a comment.
+
+## Usage
+
+```
+/plan <linearTaskId>
+```
+
+## Parameters
+
+- `linearTaskId` - Linear task ID (e.g., MOB-123)
+
+## CRITICAL: External Project Context
+
+This is for standalone Angular CLI projects (Angular 6-11). Key constraints:
+
+- **No Nx** - use Angular CLI commands (`ng build`, `ng serve`, `ng lint`)
+- **No framework** - standalone projects without @smartsoft001-mobilems packages
+- **Angular 6-11** - legacy patterns only (constructor DI, *ngIf/*ngFor, NgModules)
+- **No tests required** unless explicitly mentioned in the task
+- **No deploy** - do not plan deployment steps
+
+## Execution Steps
+
+### Step 1: Fetch Task Details
+
+1. Fetch the Linear task using `mcp__linear-server__get_issue`
+2. Read task title, description, and any attachments
+3. Fetch existing comments for context
+
+### Step 2: Analyze Codebase
+
+Understand the project structure:
+
+```bash
+# Detect project layout
+ls angular.json 2>/dev/null && echo "ROOT_ANGULAR" || echo "CHECK_APP_DIR"
+ls app/angular.json 2>/dev/null && echo "APP_DIR_ANGULAR"
+
+# Check Angular version
+cat package.json | grep '"@angular/core"' 2>/dev/null
+cat app/package.json | grep '"@angular/core"' 2>/dev/null
+
+# Check CSS framework
+cat package.json | grep -E '"bootstrap|tailwind"' 2>/dev/null
+cat app/package.json | grep -E '"bootstrap|tailwind"' 2>/dev/null
+
+# Understand project structure
+ls -la src/app/ 2>/dev/null || ls -la app/src/app/ 2>/dev/null
+```
+
+### Step 3: Identify Affected Areas
+
+Based on the task:
+1. Find relevant existing files
+2. Identify what needs to be created vs modified
+3. Check for existing patterns to follow
+4. Identify NgModules that need updating
+
+### Step 4: Create Implementation Plan
+
+Structure the plan as follows:
+
+```markdown
+## Plan Implementacji
+
+### Zadanie: [Task ID] - [Task Title]
+
+### Analiza
+
+[Brief analysis of what needs to be done and why]
+
+### Struktura Projektu
+
+- Angular: [version]
+- CSS: [Bootstrap 4 / custom SCSS / other]
+- Struktura: [app/src/ or src/]
+
+### Kroki Implementacji
+
+#### Krok 1: [Description]
+
+**Pliki do zmiany:**
+
+| Plik | Akcja | Opis |
+|------|-------|------|
+| `src/app/components/feature.component.ts` | Nowy | Komponent widoku |
+| `src/app/components/feature.component.html` | Nowy | Szablon |
+| `src/app/components/feature.component.scss` | Nowy | Style |
+| `src/app/feature.module.ts` | Modyfikacja | Dodanie deklaracji |
+
+**Wzorce:**
+- Constructor DI
+- *ngIf/*ngFor
+- [CSS approach from project]
+
+#### Krok 2: [Description]
+
+...
+
+### Weryfikacja
+
+- [ ] `ng build --prod` przechodzi bez bledow
+- [ ] Funkcjonalnosc dziala zgodnie z opisem zadania
+
+### Podzadania
+
+| ID | Tytul | Priorytet | Krok |
+|----|-------|-----------|------|
+| - | [Subtask 1] | High | 1 |
+| - | [Subtask 2] | Medium | 2 |
+```
+
+### Step 5: Create Subtasks (if needed)
+
+For complex tasks, create subtasks in Linear:
+- Use `mcp__linear-server__create_issue` with parent task ID
+- Each subtask should map to a plan step
+
+### Step 6: Post Plan as Comment
+
+Post the plan as a comment on the Linear task using `mcp__linear-server__create_comment`.
+
+### Step 7: Ask for Approval
+
+```markdown
+## Plan zapisany
+
+Plan implementacji zostal dodany jako komentarz do zadania [linearTaskId].
+
+Czy plan jest zaakceptowany? Po akceptacji uruchom `/impl [linearTaskId]` aby rozpoczac implementacje.
+```
+
+## Guidelines
+
+1. **Always analyze existing code first** before planning
+2. **Follow existing project patterns** - don't introduce new patterns
+3. **Write plan in Polish** for Linear comments
+4. **Keep steps small and focused** - one logical change per step
+5. **Don't plan tests** unless explicitly requested in the task
+6. **Don't plan deployment** steps
+7. **Identify the CSS approach** before planning UI changes
+8. **Include build verification** as the final step (`ng build --prod`)
+9. **Use Angular CLI commands** not Nx commands

package/plugins/flow-external/skills/push/SKILL.md

@@ -0,0 +1,201 @@
+---
+name: push
+description: Push changes to remote repository and update Linear task status. Shows commit summary, updates subtask statuses, and creates PR if on feature branch.
+allowed-tools:
+  - Bash
+  - Read
+  - Glob
+  - Grep
+  - AskUserQuestion
+  - 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 changes to remote and update Linear task status.
+
+## Usage
+
+```
+/push [linearTaskId]
+```
+
+## Parameters
+
+- `linearTaskId` - Linear task ID (e.g., MOB-123). Optional - will try to detect from branch name.
+
+## Execution Steps
+
+### Step 1: Check Git Status
+
+```bash
+git status
+git log origin/$(git branch --show-current)..HEAD --oneline
+```
+
+Check for:
+- Uncommitted changes (warn user)
+- Commits ahead of remote (list them)
+- Current branch name
+
+### Step 2: Detect Linear Task
+
+If `linearTaskId` not provided, try to extract from branch name:
+- Branch `MOB-123` → task `MOB-123`
+- Branch `feature/MOB-123-description` → task `MOB-123`
+
+### Step 3: Fetch Task Details
+
+If Linear task ID is available:
+1. Fetch parent task details
+2. Fetch subtasks if any
+3. Analyze completion status
+
+### Step 4: Show Summary
+
+```markdown
+## Push Summary
+
+**Branch**: `<branch-name>`
+**Commits**: X ahead of remote
+
+### Commits
+
+| Hash | Message |
+|------|---------|
+| abc1234 | feat(gallery): add lightbox |
+| def5678 | fix(gallery): fix image sizing |
+
+### Linear Task: [ID] - [Title]
+
+**Subtasks**:
+- [x] MOB-549: Completed subtask
+- [x] MOB-550: Another completed
+- [ ] MOB-551: Incomplete (reason)
+```
+
+### Step 5: Ask for Confirmation
+
+```markdown
+Do you want to push and update Linear status to "In Review"?
+```
+
+Use `AskUserQuestion` with options:
+- "Tak, push i zaktualizuj status"
+- "Nie, anuluj"
+
+### Step 6: Update Linear Status
+
+If confirmed:
+1. Update parent task status to "In Review"
+2. Update completed subtasks to "In Review"
+3. Create summary comment on parent task (in Polish):
+
+```markdown
+## Podsumowanie Implementacji
+
+### Zrealizowane Podzadania
+
+| Podzadanie | Tytul | Status |
+|-----------|-------|--------|
+| MOB-549 | [title] | Zrealizowane |
+| MOB-550 | [title] | Zrealizowane |
+
+### Niezrealizowane Podzadania
+
+| Podzadanie | Tytul | Powod |
+|-----------|-------|-------|
+| MOB-551 | [title] | [reason] |
+
+### Commity
+
+| Commit | Opis |
+|--------|------|
+| abc1234 | feat(gallery): add lightbox |
+
+### Status
+
+Task przeniesiony do "In Review".
+
+---
+
+_Raport wygenerowany przez Claude Code_
+```
+
+### Step 7: Push to Remote
+
+```bash
+git push
+```
+
+### Step 8: Branch-Specific Actions
+
+#### Feature Branch → Check/Create PR
+
+If on a feature branch (not `development` or `main`):
+
+1. Check if PR exists:
+   ```bash
+   gh pr list --head <branch-name> --base development --json number,title,state,url
+   ```
+
+2. If no PR, ask user:
+   ```markdown
+   ## Create Pull Request?
+
+   Branch `<branch-name>` has no open PR to `development`.
+   Do you want to create one?
+   ```
+
+3. If confirmed, create PR:
+   ```bash
+   gh pr create --base development --head <branch-name> --title "<Linear-ID>: <Task Title>" --body "..."
+   ```
+
+#### Development/Main Branch
+
+Just push and show confirmation.
+
+### Step 9: Final Confirmation
+
+```markdown
+## Gotowe
+
+Linear task [linearTaskId] przeniesiony do "In Review"
+Zmiany wyslane do `origin/<branch-name>`
+```
+
+## Error Handling
+
+### Push Rejected
+
+```markdown
+## Push Failed
+
+Updates were rejected. Options:
+1. `git pull --rebase` then push again
+2. `git pull` and merge
+```
+
+### No Commits to Push
+
+```markdown
+## Nothing to Push
+
+Branch is up to date with remote.
+```
+
+## Guidelines
+
+1. **Write all Linear comments in Polish**
+2. **Always confirm before status change**
+3. **Update Linear BEFORE push**
+4. **Document incomplete subtasks with reasons**
+5. **Offer PR creation on feature branches**
+6. **Do NOT monitor CI/CD pipelines**
+7. **Do NOT verify deployment**

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

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