@mmerterden/multi-agent-pipeline 14.2.2 → 15.0.0

package/pipeline/skills/shared/external/localization-reuse-map/example-mapping.json

@@ -1,19 +1,12 @@
 {
   "screen": "Sign Up  -  Account Details",
-  "platforms": [
-    "ios",
-    "android",
-    "web"
-  ],
+  "platforms": ["ios", "android", "web"],
   "figmaFileKey": "9XbExampleFigmaKey00",
-  "figmaNodes": [
-    "1024:4096",
-    "1024:4112"
-  ],
+  "figmaNodes": ["1024:4096", "1024:4112"],
   "screenshot": "screenshot.png",
   "overlay": "sign-up-account-details.overlay.png",
   "keyshots": "sign-up-account-details.keyshots.manifest.json",
-  "legacyKeyPrefix": "",
+  "legacyKeyPrefix": "Mobile-",
   "rows": [
     {
       "element": "Screen title (top bar)",
@@ -139,6 +132,56 @@
       },
       "cmsNodeId": "1024:4150",
       "cmsSource": "figma-rest"
+    },
+    {
+      "element": "Terms checkbox label",
+      "newKey": "SignUpAccountDetails.TermsLabel",
+      "new": {
+        "en": "I agree to the Terms",
+        "tr": "I agree to the Terms"
+      },
+      "legacyKeyIOS": "TermsAgree",
+      "legacyKeyAndroid": "TermsAgree",
+      "legacy": {
+        "en": "I agree to the Terms",
+        "tr": "Koşulları kabul ediyorum"
+      },
+      "verdict": "reuse",
+      "note": "New tr equals new en (untranslated in the redesign source)  -  flagging regardless of verdict; the legacy tr value is fine to reuse once the redesign copy is translated."
+    },
+    {
+      "element": "Referral code field label",
+      "newKey": "SignUpAccountDetails.ReferralLabel",
+      "new": {
+        "en": "Referral code (optional)",
+        "tr": "Referans kodu (opsiyonel)"
+      },
+      "legacyKeyIOS": "",
+      "legacyKeyAndroid": "",
+      "legacy": {},
+      "verdict": "new",
+      "note": "No legacy equivalent existed for this field. CMS tr ('varsa') diverges from the new tr ('opsiyonel')  -  content team's final copy, flagged not hidden.",
+      "cms": {
+        "tr": "Referans kodu (varsa)"
+      },
+      "cmsNodeId": "1024:4158",
+      "cmsSource": "figma-rest"
+    },
+    {
+      "element": "Required-field validation message (any field left empty)",
+      "newKey": "SignUpAccountDetails.Error.<field>Required",
+      "new": {
+        "en": "This field is required",
+        "tr": "Bu alan zorunludur"
+      },
+      "legacyKeyIOS": "Error.<field>Required",
+      "legacyKeyAndroid": "error_<field>_required",
+      "legacy": {
+        "en": "This field is required",
+        "tr": "Bu alan zorunludur"
+      },
+      "verdict": "review",
+      "note": "Dynamic  -  enumerate at runtime: the key itself is built as \"Error.\\(field)Required\".localized with `field` interpolated (FirstName/LastName/Email/Password), so no single static key exists to cross-reference; scan-screen-keys.py surfaces the pattern as a dynamic hit and every concrete field must be enumerated and mapped."
     }
   ]
 }

package/pipeline/skills/shared/external/localization-reuse-map/reference/sources-and-recipes.md

@@ -61,10 +61,10 @@ keys: map once where that component is mapped  -  flag, don't duplicate per scre
 2. **iOS  -  follow the chain.** Fetch the VM raw; it builds sections/cells. Form-field labels are **not** in
    the VM  -  they default inside the **cell presentation models** it instantiates. Follow them:
    ```bash
-   gh api ".../contents/<path>/TKSStandaloneAddPassengerViewModel.swift" -H "Accept: application/vnd.github.raw" > /tmp/vm.swift
+   gh api ".../contents/<path>/<Screen>ViewModel.swift" -H "Accept: application/vnd.github.raw" > /tmp/vm.swift
    grep -nE 'PresentationModel|\.localized' /tmp/vm.swift          # find the cell classes it creates
    # then fetch each cell class and grep its keys:
-   gh api ".../Forms/TextInputCell/PresentationModels/TKSPnrSurnameTextInputCellPresentationModel.swift" -H "Accept: application/vnd.github.raw" | grep -oE '"[^"]+"\.localized'
+   gh api ".../Forms/TextInputCell/PresentationModels/<Field>TextInputCellPresentationModel.swift" -H "Accept: application/vnd.github.raw" | grep -oE '"[^"]+"\.localized'
    ```
    This is how `NewSurnameReq` / `PnrNumber` / `ReservationEticketPlaceHolder` surface  -  a VM-only grep
    misses them. Keys are the string literal before `.localized`.
@@ -156,7 +156,8 @@ builders, VM error branches  -  not the VC→VM→cell chain) and to **dynamic/i
 ```bash
 python3 scripts/scan-screen-keys.py --screen-path <impl-screen-dir>     # [--category error|dynamic|static]
 ```
-It greps `.swift`/`.kt`/`.xml` and classifies each hit `static | error | dynamic` with file:line. **Fold the
+It greps `.swift`/`.kt`/`.xml`/`.ts`/`.tsx`/`.js`/`.jsx`/`.vue` and classifies each hit `static | error |
+dynamic` with file:line. **Fold the
 `error` and `dynamic` hits into the mapping** (each still gets the normal new/legacy/CMS resolution); diff the
 `static` hits against the registry union to catch keys wired in code but absent from the registry. Dynamic
 keys that can't be statically resolved are mapped with a note (`verdict: review` / "dynamic  -  enumerate at

package/pipeline/skills/skills-index.md

@@ -3,7 +3,7 @@
 > Auto-generated by `pipeline/scripts/build-skills-index.mjs`  -  do not hand-edit.
 > Regenerate with `node pipeline/scripts/build-skills-index.mjs`.
 
-**202 skills** across 2 groups.
+**205 skills** across 2 groups.
 
 | Group | Name | Platform | Description |
 |-------|------|----------|-------------|
@@ -79,6 +79,7 @@
 | external | `ios-debugger-agent` |  -  | Debug the current iOS project on a booted simulator with XcodeBuildMCP. Use when an iOS bug has to be reproduced and diagnosed on a booted s |
 | external | `ios-developer` |  -  | Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimiz |
 | external | `ios-localization` |  -  | Implement, review, or improve localization and internationalization in iOS/macOS apps  -  String Catalogs (.xcstrings), generated localizabl |
+| external | `ios-module-structure` |  -  | The ios-module-structure rule registry: stable-ID rules over where a declaration lives, what its file is called and what its folder must con |
 | external | `ios-networking` |  -  | Build, review, or improve networking code in iOS/macOS apps using URLSession with async/await, structured concurrency, and modern Swift patt |
 | external | `ios-security` |  -  | Secure iOS apps with Keychain Services, CryptoKit encryption, biometric authentication (Face ID, Touch ID), Secure Enclave key storage, LACo |
 | external | `ios-simulator` |  -  | Manages iOS Simulator devices and tests app behaviour with xcrun simctl: device lifecycle, app install and launch, push notification and loc |
@@ -92,10 +93,11 @@
 | external | `monorepo-architect` |  -  | Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient mu |
 | core | `multi-agent` |  -  | Task orchestrator: runs the full pipeline from a Jira ID or GitHub Issue URL  -  analysis → plan → TDD development → parallel review (Fable  |
 | core | `multi-agent-analysis` |  -  | Standalone feature-spec analysis (v3 template). Platform-agnostic concept layer with repo-driven convention extraction and per-platform Pass |
-| core | `multi-agent-analysis-resolve` |  -  | Resolve the Section 20 Risks and Open Questions of an analysis v3 document one row at a time. Proposes up to 3 source-labeled answer candida |
+| core | `multi-agent-analysis-resolve` |  -  | Resolve the Section 20 Risks and Open Questions of an analysis v3 document one row at a time: up to 3 source-labeled answer candidates per r |
 | core | `multi-agent-autopilot` |  -  | Launch any task in autopilot mode: skips every confirmation, runs end-to-end autonomously. Use when a task should run end to end with no con |
 | core | `multi-agent-build-optimize` |  -  | Wrapper that dispatches to xcode-build-orchestrator on iOS repos. Benchmarks the current Xcode build, runs compilation / project / SPM analy |
 | core | `multi-agent-channels` |  -  | Multi-channel reporter  -  Jira/Confluence/Wiki/PR description. Multi-select channels + content, humanizer pass, reviewer-preserving Bitbuck |
+| core | `multi-agent-complaint-analysis` |  -  | Customer-complaint triage. Ingests complaints (paste, csv/xlsx/txt/json file, Jira issue, Confluence URL), fetches Graylog evidence per trx/ |
 | core | `multi-agent-create-jira` |  -  | Create a standards-compliant Jira issue (Task / Bug / Story): asks the type, mines project conventions, drafts from a standard template with |
 | core | `multi-agent-design-check` |  -  | Mock-mode vs Figma design audit (iOS / Android, local-only). Pick repo + module, gate on mock support, enumerate every state driver into a c |
 | core | `multi-agent-dev` |  -  | Fast development mode: Init → Dev (Opus) → Review → Test → Commit → Report. Analysis and planning are skipped, review is not. Use when the w |
@@ -116,9 +118,11 @@
 | core | `multi-agent-log` |  -  | Show the agent-log.md for the given task. With no ID, shows the most recent task. Use when asked what a task did, or to read its log. |
 | core | `multi-agent-manual-test` |  -  | Switch to the active task's branch and prepare it for manual testing in Xcode. Phase 5 standalone (the UI Bug Hunter lives at multi-agent-te |
 | core | `multi-agent-prune-logs` |  -  | Delete per-task project logs under ~/.claude/logs/multi-agent (filter by age/project/task). Audit trail + metrics are preserved. Dry-run fir |
+| core | `multi-agent-prune-prompts` |  -  | Zero-base prompt review: measure the always-on instruction footprint, classify every rule block, propose keep/trial-removal/delete; applies  |
 | core | `multi-agent-purge` |  -  | ⚠️ Wipes every worktree, branch, log, and state file. Irreversible; asks for double confirmation. Use when every worktree, branch, log and s |
 | core | `multi-agent-refactor` |  -  | Analyse the project: extract adapted best-practices, hunt real bugs + improvement areas, check upstream drift of derived skills, research th |
 | core | `multi-agent-resume` |  -  | Resume a stopped or failed task from the phase where it left off. Use when a task stopped or failed and should carry on from where it left o |
+| core | `multi-agent-resume-local` |  -  | Continue already-done LOCAL work through the pipeline tail: Review → Build+Test → Commit/PR → Report (technical analysis + Jira test-scenari |
 | core | `multi-agent-review` |  -  | Run parallel review on a branch diff or a Pull Request: 2 models on Claude Code (Fable + Sonnet), 3 models on Copilot CLI (GPT + Opus + Sonn |
 | core | `multi-agent-review-issue` |  -  | Assess whether a GitHub issue is ready for multi-agent development: fetch it, grade scope / acceptance criteria / repro / design / API / sta |
 | core | `multi-agent-review-jira` |  -  | Assess whether a Jira issue is ready for multi-agent development: fetch it, grade scope / acceptance criteria / repro / design / API / stack |
@@ -127,8 +131,7 @@
 | core | `multi-agent-scan` |  -  | Skill security scan: walks local skill directories against a tiered pattern catalog. Use when local skill directories need checking for unsa |
 | core | `multi-agent-search` |  -  | Log search across every agent-log.md with smart ranking and filters. Optional --semantic flag queries the per-repo triage corpus. Use when s |
 | core | `multi-agent-setup` |  -  | First-run setup wizard: keychain token discovery, Git Identity onboarding, and pipeline preparation. Use when the pipeline is being set up f |
-| core | `multi-agent-ship` |  -  | Continue already-done LOCAL work through the pipeline tail: Review → Build+Test → Commit/PR → Report (technical analysis + Jira test-scenari |
-| core | `multi-agent-stack` |  -  | Select the active stack for this repo by enabling the matching marketplace plugin(s) in .claude/settings.json (ios/android/mobile/backend/fr |
+| core | `multi-agent-stack` |  -  | Select the active stack(s) for this repo by enabling the matching marketplace plugin(s) in .claude/settings.json. Multi-select: pass several |
 | core | `multi-agent-status` |  -  | Show every multi-agent task's ID, phase, branch, and status. Use when asked what is running, or for an overview of every task. |
 | core | `multi-agent-store-ready` |  -  | Pre-submission store readiness for a built package, iOS and Android, local-only. Three symmetric gates per platform: a static package audit, |
 | core | `multi-agent-sync` |  -  | One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and the dev-toolkit MCP server. Use whe |