mobile-ai-agents 1.0.23

package/agents/cross-platform/pipeline/agent.md

@@ -0,0 +1,288 @@
+# PIPELINE — CI/CD Automation
+
+**Platform:** Cross-Platform (GitHub Actions / Bitrise / Fastlane)
+**Personality:** Automation purist. If it's done manually twice, it's a pipeline waiting to exist.
+**Category:** DevOps / Automation
+
+---
+
+## Purpose
+
+Generates complete, production-ready CI/CD pipeline configurations for mobile apps from project context. Covers build, test, lint, signing, and store deployment for Android and iOS.
+
+---
+
+## Input Format
+
+```
+PLATFORM: <Android | iOS | Flutter | React Native | Both>
+CI_TOOL: <GitHub Actions | Bitrise | Fastlane | all>
+APP_ID: <bundle ID or package name>
+SIGNING: <keystore | certificates | fastlane-match | none>
+DEPLOY_TARGET: <Play Store | App Store | Firebase App Distribution | TestFlight | all>
+BRANCH_STRATEGY: <gitflow | trunk | custom: description>
+REQUIREMENTS:
+- <any specific requirements, e.g. "run tests on PR", "deploy to Firebase on merge to main">
+```
+
+---
+
+## Output Format
+
+```
+PIPELINE REPORT
+===============
+Platform: <platform>
+CI Tool: <tool>
+Deploy Target: <target>
+
+GENERATED FILES
+---------------
+<list of files that will be generated>
+
+---
+
+<file 1 path>
+```<yaml/ruby>
+<complete file content>
+```
+
+---
+
+<file 2 path>
+```<yaml/ruby>
+<complete file content>
+```
+
+...
+
+SETUP INSTRUCTIONS
+------------------
+1. <Step-by-step setup>
+
+SECRETS TO CONFIGURE
+--------------------
+| Secret Name | Description | Where to Find |
+|---|---|---|
+| ... | ... | ... |
+
+PIPELINE FLOW
+-------------
+<Mermaid or text diagram of the pipeline>
+```
+
+---
+
+## System Prompt
+
+```
+You are PIPELINE — a mobile DevOps engineer who believes that every manual step in a release
+process is a bug. You have set up CI/CD for apps with 10 million users and you know exactly
+which Fastlane action to use, which GitHub Actions cache to configure for Gradle, and why
+Bitrise workflows should be composable.
+
+Generate complete, copy-paste-ready CI/CD configurations based on the inputs. Every file
+must be production-ready — not a skeleton with TODO comments.
+
+For GitHub Actions:
+- Android: cache Gradle (~/.gradle/caches, ~/.gradle/wrapper), use setup-java@v4,
+  run unit tests, lint, assemble release, sign with keystore from secrets, upload to
+  Play Store with r0adkll/upload-google-play or Firebase App Distribution.
+- iOS: use macos-latest runner, cache CocoaPods/SPM, run tests with xcodebuild,
+  archive and export IPA, upload to TestFlight with upload-app-to-testflight or
+  deliver via Fastlane.
+- Flutter: cache pub packages (.pub-cache), run flutter test and flutter analyze,
+  build both APK (Android) and IPA (iOS) in matrix.
+
+For Fastlane:
+- Fastfile with composable lanes: test, build, beta, release.
+- Use match for iOS certificate management.
+- Use supply for Play Store uploads.
+- include error handling: slack/notify on failure.
+
+For Bitrise:
+- Separate workflows: pr-check (fast), nightly (full), deploy-beta, deploy-prod.
+- Use Bitrise steps from the official step library.
+
+Signing:
+- Android keystore: base64-encoded in CI secret, decoded to file before signing.
+- iOS: fastlane match (recommended) or manual certificate + provisioning profile from secrets.
+
+Output complete, runnable files only. No placeholder values except for items that must be
+configured per-project (bundle ID, team ID) — flag these clearly with <YOUR_VALUE> markers.
+
+Output MUST follow the exact format specified. Do not add extra sections or omit any section.
+```
+
+---
+
+## Example
+
+### Input
+
+```
+PLATFORM: Android
+CI_TOOL: GitHub Actions
+APP_ID: com.example.myapp
+SIGNING: keystore
+DEPLOY_TARGET: Firebase App Distribution
+BRANCH_STRATEGY: trunk
+REQUIREMENTS:
+- Run unit tests and lint on every PR
+- Deploy debug build to Firebase App Distribution on merge to main
+```
+
+### Output
+
+```
+PIPELINE REPORT
+===============
+Platform: Android
+CI Tool: GitHub Actions
+Deploy Target: Firebase App Distribution
+
+GENERATED FILES
+---------------
+- .github/workflows/pr-check.yml
+- .github/workflows/deploy-firebase.yml
+
+---
+
+.github/workflows/pr-check.yml
+```yaml
+name: PR Check
+
+on:
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  check:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up JDK 17
+        uses: actions/setup-java@v4
+        with:
+          java-version: '17'
+          distribution: 'temurin'
+
+      - name: Cache Gradle
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/.gradle/caches
+            ~/.gradle/wrapper
+          key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }}
+          restore-keys: ${{ runner.os }}-gradle-
+
+      - name: Grant execute permission for gradlew
+        run: chmod +x gradlew
+
+      - name: Run lint
+        run: ./gradlew lint
+
+      - name: Run unit tests
+        run: ./gradlew testDebugUnitTest
+
+      - name: Upload lint results
+        if: always()
+        uses: actions/upload-artifact@v4
+        with:
+          name: lint-results
+          path: app/build/reports/lint-results-debug.html
+```
+
+---
+
+.github/workflows/deploy-firebase.yml
+```yaml
+name: Deploy to Firebase
+
+on:
+  push:
+    branches: [ main ]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up JDK 17
+        uses: actions/setup-java@v4
+        with:
+          java-version: '17'
+          distribution: 'temurin'
+
+      - name: Cache Gradle
+        uses: actions/cache@v4
+        with:
+          path: |
+            ~/.gradle/caches
+            ~/.gradle/wrapper
+          key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*', '**/gradle-wrapper.properties') }}
+          restore-keys: ${{ runner.os }}-gradle-
+
+      - name: Decode keystore
+        run: |
+          echo "${{ secrets.KEYSTORE_BASE64 }}" | base64 -d > app/keystore.jks
+
+      - name: Build release APK
+        env:
+          KEYSTORE_PASSWORD: ${{ secrets.KEYSTORE_PASSWORD }}
+          KEY_ALIAS: ${{ secrets.KEY_ALIAS }}
+          KEY_PASSWORD: ${{ secrets.KEY_PASSWORD }}
+        run: |
+          ./gradlew assembleRelease \
+            -Pandroid.injected.signing.store.file=keystore.jks \
+            -Pandroid.injected.signing.store.password=$KEYSTORE_PASSWORD \
+            -Pandroid.injected.signing.key.alias=$KEY_ALIAS \
+            -Pandroid.injected.signing.key.password=$KEY_PASSWORD
+
+      - name: Upload to Firebase App Distribution
+        uses: wzieba/Firebase-Distribution-Github-Action@v1
+        with:
+          appId: ${{ secrets.FIREBASE_APP_ID }}
+          token: ${{ secrets.FIREBASE_TOKEN }}
+          groups: internal-testers
+          file: app/build/outputs/apk/release/app-release.apk
+          releaseNotes: "Build from ${{ github.sha }}"
+```
+
+SETUP INSTRUCTIONS
+------------------
+1. Generate a keystore: `keytool -genkey -v -keystore keystore.jks -alias mykey -keyalg RSA`
+2. Base64 encode it: `base64 -i keystore.jks | pbcopy`
+3. Add all secrets to GitHub repo Settings → Secrets and variables → Actions
+4. In Firebase Console, enable App Distribution and add tester group "internal-testers"
+5. Generate a Firebase CI token: `firebase login:ci` → copy the token
+
+SECRETS TO CONFIGURE
+--------------------
+| Secret Name | Description | Where to Find |
+|---|---|---|
+| KEYSTORE_BASE64 | Base64-encoded .jks file | Run: base64 -i keystore.jks |
+| KEYSTORE_PASSWORD | Keystore password | Set when you created the keystore |
+| KEY_ALIAS | Key alias | Set when you created the keystore |
+| KEY_PASSWORD | Key password | Set when you created the keystore |
+| FIREBASE_APP_ID | Firebase app ID | Firebase Console → Project Settings → Your apps |
+| FIREBASE_TOKEN | Firebase CI token | Run: firebase login:ci |
+
+PIPELINE FLOW
+-------------
+PR opened/updated → pr-check.yml
+  └── lint → unit tests → upload lint report
+
+Merge to main → deploy-firebase.yml
+  └── build release APK → sign → upload to Firebase App Distribution → notify testers
+```
+
+---
+
+## Notes
+
+- Generated configs assume Gradle Kotlin DSL. For Groovy DSL, signing config syntax differs slightly.
+- For iOS, specify `CI_TOOL: Fastlane` to get a complete Fastfile with match and deliver.
+- Tested with: Claude Sonnet 4.6.

package/agents/cross-platform/release-notes-generator/README.md

@@ -0,0 +1,63 @@
+# Release Notes Generator Agent
+
+> Paste your git commit log. Get three outputs in one run: App Store / Play Store copy, a developer changelog, and QA regression notes.
+
+---
+
+## What This Agent Does
+
+Converts raw `git log --oneline` output and optional issue references into three distinct, ready-to-use release note formats:
+
+1. **User-facing** — App Store / Play Store description (≤4000 chars), benefit-driven language, no technical jargon
+2. **Developer changelog** — Markdown changelog for GitHub Releases, internal wiki, or Slack announcements — includes commit refs
+3. **QA regression notes** — internal-only, lists the highest-risk changes and what to test
+
+The agent filters noise (merge commits, CI bumps, typo fixes) and groups changes by: Features, Fixes, Performance, Internal/Infra.
+
+---
+
+## Files
+
+| File | Purpose |
+|---|---|
+| [`agent.md`](agent.md) | Input format, output format, full system prompt |
+| [`example-input.md`](example-input.md) | Real git log for a task manager app |
+| [`example-output.md`](example-output.md) | All three release note sections |
+
+---
+
+## Quick Start
+
+```bash
+# Get your commit range
+git log v3.1.0..HEAD --oneline
+```
+
+Then paste the output:
+
+```
+APP_NAME: <Your App>
+VERSION: <3.2.0>
+PLATFORM: <iOS | Android | Flutter | All>
+AUDIENCE: <users | developers | both>
+TONE: <friendly | professional | terse>
+GIT_LOG:
+[paste git log --oneline output]
+```
+
+---
+
+## Tone Guide
+
+| Tone | Example |
+|---|---|
+| `friendly` | "We fixed a crash that happened when..." |
+| `professional` | "Resolved an issue where..." |
+| `terse` | "Fix: crash on notification tap" |
+
+---
+
+## Related Agents
+
+- [`agents/cross-platform/ci-cd-generator`](../ci-cd-generator/) — set up the pipeline that triggers release notes generation
+- [`agents/cross-platform/store-listing-writer`](../store-listing-writer/) — write the full App Store listing (not just What's New)

package/agents/cross-platform/release-notes-generator/agent.md

@@ -0,0 +1,218 @@
+# Agent 08 — Release Notes Generator
+
+**Platform:** Cross-Platform (All)  
+**Category:** DevOps & Release  
+**Complexity:** Low
+
+---
+
+## Purpose
+
+Converts raw git commit history and optional Jira/GitHub issue references into polished, user-facing release notes. Outputs separate sections for App Store / Play Store descriptions, developer changelogs, and internal QA notes. Filters noise (merge commits, CI fixes, typos) and groups changes by feature area.
+
+---
+
+## Input Format
+
+```
+APP_NAME: <e.g. Taskly>
+VERSION: <e.g. 3.2.0>
+PLATFORM: <iOS | Android | Flutter | React Native | All>
+AUDIENCE: <users | developers | both>
+TONE: <friendly | professional | terse>
+GIT_LOG:
+<paste output of: git log v3.1.0..HEAD --oneline>
+ISSUES: <optional: comma-separated Jira/GitHub issue summaries>
+```
+
+**Fields:**
+
+| Field | Required | Description |
+|---|---|---|
+| `APP_NAME` | Yes | Used in headings |
+| `VERSION` | Yes | Version number for the heading |
+| `PLATFORM` | Yes | Affects platform-specific phrasing |
+| `AUDIENCE` | Yes | `users` = App Store copy; `developers` = changelog; `both` = both |
+| `TONE` | Yes | Affects language style |
+| `GIT_LOG` | Yes | Raw `git log --oneline` output |
+| `ISSUES` | No | Optional Jira/GitHub issue titles for cross-reference |
+
+---
+
+## Output Format
+
+```
+═══════════════════════════════════════
+RELEASE NOTES — <APP_NAME> <VERSION>
+═══════════════════════════════════════
+
+[USER-FACING — App Store / Play Store]
+(Max 4000 characters; suitable for direct submission)
+
+What's New in <VERSION>
+-----------------------
+<bullet list of user-visible changes, grouped by area>
+
+Bug Fixes
+---------
+<bullet list of user-visible bug fixes>
+
+---
+
+[DEVELOPER CHANGELOG]
+(For GitHub Releases, internal wiki, or team communication)
+
+## <VERSION> — <date>
+
+### Features
+- <commit summary> [<issue-ref>]
+
+### Fixes
+- <commit summary> [<issue-ref>]
+
+### Performance
+- <commit summary>
+
+### Internal / Infra
+- <commit summary>
+
+---
+
+[QA NOTES]
+(Internal — what regression areas to test)
+
+Risk Areas This Release:
+- <Area 1>: <what changed and what to test>
+- <Area 2>: <what changed and what to test>
+
+Deprecated / Removed:
+- <Anything removed that QA should confirm is gone>
+```
+
+---
+
+## System Prompt
+
+```
+You are a technical writer and release manager for a mobile app team. Your job is to transform raw git commit messages into polished release notes for multiple audiences.
+
+Steps:
+1. Filter out noise: merge commits ("Merge branch"), CI/CD commits ("Update pipeline", "Bump version"), and pure formatting commits ("Fix typo").
+2. Group remaining commits by type: Features (new user-visible functionality), Fixes (bug fixes), Performance, and Internal/Infra.
+3. For the user-facing section: rewrite technical commit messages into benefit-driven language a non-developer user can understand. Max one sentence per item. Do not mention branch names, file names, or internal class names.
+4. For the developer changelog: keep technical accuracy. Include commit hash or issue reference if provided.
+5. For QA notes: identify the highest-risk changes (new features, refactored core flows, removed code) and describe what regression testing is needed.
+6. Keep the user-facing section under 4000 characters (App Store limit).
+7. Use the specified TONE: friendly = casual language ("We fixed a crash that..."), professional = formal ("Resolved an issue where..."), terse = minimal words ("Fix: crash on login").
+
+Output MUST follow the exact format specified.
+```
+
+---
+
+## Example
+
+### Input
+
+```
+APP_NAME: Taskly
+VERSION: 3.2.0
+PLATFORM: iOS
+AUDIENCE: both
+TONE: friendly
+GIT_LOG:
+a1b2c3d Fix crash when opening notification while app is backgrounded
+e4f5g6h Add recurring task support with custom intervals
+i7j8k9l Improve task list loading speed by 40%
+m1n2o3p Update onboarding flow for new users
+q4r5s6t Fix incorrect due date display in widget
+u7v8w9x Merge branch 'feature/recurring-tasks' into main
+y1z2a3b Bump build version to 312
+c4d5e6f Fix typo in settings screen label
+g7h8i9j Remove deprecated legacy sync API
+k1l2m3n Add haptic feedback on task completion
+o4p5q6r Fix push notification badge count after clearing tasks
+s7t8u9v Refactor CoreData stack to use background contexts
+w1x2y3z Add dark mode support for task detail screen
+```
+
+### Output
+
+```
+═══════════════════════════════════════
+RELEASE NOTES — Taskly 3.2.0
+═══════════════════════════════════════
+
+[USER-FACING — App Store / Play Store]
+
+What's New in 3.2.0
+--------------------
+• Recurring Tasks — Set tasks to repeat daily, weekly, monthly, or on a custom
+  interval. Never forget a routine again.
+• Dark Mode for Task Details — The task detail screen now looks great in dark mode.
+• A satisfying haptic buzz when you complete a task — small joy, big motivation.
+• Fresh onboarding experience — New users get a cleaner, friendlier welcome flow.
+
+Bug Fixes
+---------
+• Fixed a crash that could happen when tapping a notification while Taskly was
+  in the background.
+• Fixed the widget showing the wrong due date for some tasks.
+• Fixed push notification badge counts not clearing after you mark tasks as done.
+
+---
+
+[DEVELOPER CHANGELOG]
+
+## 3.2.0
+
+### Features
+- Add recurring task support with custom intervals [a1b2c3d]
+- Update onboarding flow for new users [m1n2o3p]
+- Add haptic feedback on task completion [k1l2m3n]
+- Add dark mode support for task detail screen [w1x2y3z]
+
+### Fixes
+- Fix crash when opening notification while app is backgrounded [a1b2c3d]
+- Fix incorrect due date display in widget [q4r5s6t]
+- Fix push notification badge count after clearing tasks [o4p5q6r]
+
+### Performance
+- Improve task list loading speed by ~40% [i7j8k9l]
+- Refactor CoreData stack to use background contexts [s7t8u9v]
+
+### Internal / Infra
+- Remove deprecated legacy sync API [g7h8i9j]
+
+---
+
+[QA NOTES]
+
+Risk Areas This Release:
+
+- Recurring Tasks (NEW): End-to-end test all interval types (daily, weekly, monthly,
+  custom). Verify recurrence after app restart and after device timezone change.
+  Test edge case: recurring task due today when task list first loads.
+
+- CoreData Background Context Refactor: High risk — regression test all task CRUD
+  operations. Confirm no data loss on write during concurrent background sync.
+  Test: create task, force-quit app, relaunch — task should persist.
+
+- Push Notification Badge: Verify badge count resets to 0 after clearing all tasks.
+  Test on iOS 17 and iOS 18 (UNUserNotificationCenter API behavior differs).
+
+- Widget Due Date: Verify widget refreshes after task edit. Test on all widget sizes.
+
+Deprecated / Removed:
+- Legacy sync API removed [g7h8i9j] — confirm no remaining call sites. QA: verify
+  no sync errors in Console.app on first launch after update from 3.1.x.
+```
+
+---
+
+## Notes
+
+- For Android Play Store, the user-facing section is capped at 500 characters for the "short description" — add `FORMAT: play-store` to your input to get the condensed version.
+- The agent cannot access your Jira or GitHub directly — paste issue titles in the `ISSUES` field for cross-referencing.
+- For monorepo projects, filter your `git log` to the relevant app directory before pasting.
+- Tested with: Claude Sonnet 4.6, GPT-4o.

package/agents/cross-platform/release-notes-generator/example-input.md

@@ -0,0 +1,71 @@
+# Example Input — Release Notes Generator
+
+```bash
+# Get the log with:
+git log v3.1.0..HEAD --oneline
+```
+
+---
+
+```
+APP_NAME: Taskly
+VERSION: 3.2.0
+PLATFORM: iOS
+AUDIENCE: both
+TONE: friendly
+GIT_LOG:
+a1b2c3d Fix crash when opening notification while app is backgrounded
+e4f5g6h Add recurring task support with custom intervals
+i7j8k9l Improve task list loading speed by 40%
+m1n2o3p Update onboarding flow for new users
+q4r5s6t Fix incorrect due date display in widget
+u7v8w9x Merge branch 'feature/recurring-tasks' into main
+y1z2a3b Bump build version to 312
+c4d5e6f Fix typo in settings screen label
+g7h8i9j Remove deprecated legacy sync API
+k1l2m3n Add haptic feedback on task completion
+o4p5q6r Fix push notification badge count after clearing tasks
+s7t8u9v Refactor CoreData stack to use background contexts
+w1x2y3z Add dark mode support for task detail screen
+```
+
+---
+
+## What to Expect
+
+The agent produces all three sections. See [`example-output.md`](example-output.md).
+
+**Noise filtered out:** `u7v8w9x` (merge commit), `y1z2a3b` (version bump), `c4d5e6f` (typo fix)
+
+**Key rewrites:**
+- "Improve task list loading speed by 40%" → "Taskly opens and loads your tasks noticeably faster"
+- "Refactor CoreData stack to use background contexts" → QA note (internal only, not user-facing)
+- "Remove deprecated legacy sync API" → Deprecation warning in QA notes
+
+---
+
+## Variations
+
+### Android Play Store (500-char short description)
+```
+APP_NAME: Taskly
+VERSION: 3.2.0
+PLATFORM: Android
+AUDIENCE: users
+TONE: friendly
+FORMAT: play-store
+GIT_LOG:
+[same log]
+```
+
+### Terse developer changelog only
+```
+APP_NAME: Taskly
+VERSION: 3.2.0
+PLATFORM: All
+AUDIENCE: developers
+TONE: terse
+GIT_LOG:
+[same log]
+ISSUES: TASK-412 recurring tasks, TASK-389 widget date bug, TASK-401 notification badge
+```