@1aboveio/skills 1.0.16 → 1.0.17

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@1aboveio/skills",
-  "version": "1.0.16",
+  "version": "1.0.17",
   "description": "Every 1aboveio skill package in one: install once, then choose which packages Pi loads with npx @1aboveio/skills select.",
   "license": "MIT",
   "repository": {
@@ -28,8 +28,8 @@
   "nativeCodex": {
     "schemaVersion": 1,
     "metadataPath": ".codex-plugin/resources.json",
-    "metadataDigest": "efea727f2b53be74c1dad921e4d976e9a4bf22054a5461217bea9a5983de48cc",
-    "releaseIdentity": "357a73a8819a5c43f9e6d935ece7e5efc38519d0b83e0984798677c4cb9dfc0d"
+    "metadataDigest": "4ae04aa79316f8a7cc9df45582d19e332321316012dac6843be1eb21d2b1a385",
+    "releaseIdentity": "d4a51368dcc414b3136d3b6f51a6aeeeea77429a101eb65f36f7878e00032494"
   },
   "pi": {
     "skills": [
@@ -260,7 +260,7 @@
         ]
       }
     ],
-    "digest": "26eb35331224e4dd2e0e8ef13bafd6383af21ae416bcf9e5acc28e68c6b45221"
+    "digest": "ae9b2ca5b33484b68e892b41976bcc054562385ef7dc7db94bf86ab42e369d0d"
   },
   "publishConfig": {
     "registry": "https://registry.npmjs.org/",

package/skills/app-dev/airflow/SKILL.md

@@ -2,7 +2,7 @@
 name: airflow
 description: Airflow DAG architecture and conventions. Use when designing, writing, reviewing, testing, or debugging Airflow DAGs and tasks, including TaskGroups, data intervals, timezone-aware date parameters, CLI validation, environment-based scheduling, and pytest integrity tests.
 user-invocable: true
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Airflow DAG Development Patterns

package/skills/app-dev/android-development/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: android-development
 description: "Prove and debug Expo / React Native apps on an owned Android emulator. Use for Android startup/rendering failures, Metro or ADB problems, UiAutomator/harness failures, APK builds, SDK/NDK/JDK workspace setup, native journey validation, and choosing Kotlin/Compose versus React Native for Android flows. Reproduce failed Android CI checkpoints off CI before fixing and redispatching. Standalone invocation offers Project or Session; init persists repo conventions. NOT for workflow YAML, CI speed or runners (github-actions), browser tests (e2e-test), iOS (ios-foundation), plain Jest tests, or signing/store release."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Android development
@@ -60,13 +60,15 @@ The contract, other languages and the Maestro/Detox mapping are in
 
 ## UI journey tool
 
-The skill references Maestro; it does not bundle or install it. A repo with no journey tool
-is offered Maestro for new single-device journeys; a repo with a working harness keeps it
-and adds Maestro flows alongside. Run it on the session's own emulator
-(`maestro --device <serial>`) and convert its output with
+The skill references Maestro; it does not bundle or install it. Offer Maestro for new
+single-device journeys when the repo has no journey tool. Keep an existing sufficient
+harness; adding Maestro needs a concrete benefit and repo authorization, not just an
+installed CLI. Maestro uses the same work loop and validation ladder. Run it on the
+session's own emulator (`maestro --device <serial>`) and convert its output with
 [maestro_failure.py](scripts/maestro_failure.py), which writes the record above. Read
-[UI journeys](references/ui-journeys.md) for the device-ownership cost, evidence layout, MCP
-use and the cases that stay custom.
+[UI journeys](references/ui-journeys.md) before selecting or running Maestro flows, for
+starting state, permissions, device ownership, execution evidence and the cases that
+stay custom.
 
 ## Validation ladder
 

package/skills/app-dev/android-development/references/feature-work.md

@@ -173,8 +173,9 @@ at L2. Required CI and L3 obligations remain assigned, not silently waived or ma
   rule for unreproduced or intermittent failures; report uncertainty until evidence
   supports the cause.
 - Report source SHA, commands, results and remaining gaps at review handoff. For device
-  checks, include the selected scenarios, `PASS` markers and cleanup exit. For a failure,
-  name the earliest failing checkpoint and link retained evidence; preserve failed attempts.
+  checks, include the selected scenarios, per-scenario results (`PASS` markers or the
+  journey tool's report) and cleanup exit. For a failure, name the earliest failing
+  checkpoint and link retained evidence; preserve failed attempts.
   Separate build duration, device-check duration and total worker time when discussing cost.
   Reuse existing logs to distinguish cold/warm builds, build count, ABI, test packaging,
   runtime startup and edit-to-feedback time. Do not infer a task's cost from total job time,

package/skills/app-dev/android-development/references/gotchas.md

@@ -20,8 +20,10 @@ the product.
 | Backend tool, CI only | a Backend-backed step gets a 5xx in CI only; the log names a missing program (`Browser was not found at the configured executablePath`) |
 | adb transport, mid-journey | `connection terminated: read failed` in the adb trace after boot, then lost `adb reverse`: usually guest RAM |
 | UiAutomator server | `RemoteDisconnected` while the adb transport stays up: the on-device server was relaunched |
+| Maestro driver | driver readiness fails while a setup uiautomator2 process is still alive: see [device ownership](ui-journeys.md#device-ownership) |
 | Journey harness | a wait right after a navigation times out while the destination is on screen |
 | Journey harness, short screen | a wait for a label times out only on a short or landscape screen, which shows the content above it |
+| Journey adapter | an offscreen target stays hidden while scrolls move away from it |
 | Product assertion | a screen or state mismatch with a screenshot |
 
 Then match the signal against [gotchas.md](gotchas.md). If nothing
@@ -143,6 +145,17 @@ matches, [confirm the suspected cause](#confirm-a-suspected-cause) before changi
 
 ## Journey harness
 
+### A scroll adapter moves away from the target
+
+- **Signal:** a custom comparison adapter times out on an offscreen target even though it
+  sends scroll gestures; a fake UI that exposes all targets can still pass.
+- **Cause:** Maestro's requested scroll direction describes the content to reach, not the
+  finger movement. Mapping `DOWN` to a downward finger swipe reverses the intended scroll.
+- **Fix:** for `DOWN` toward later content, swipe the finger up; for `UP` toward earlier
+  content, swipe the finger down. In the adapter test, keep the target offscreen until the
+  correct gesture moves it into view. Wrong-direction gestures must not reveal it merely
+  because a gesture count was reached. Check both directions where the adapter supports them.
+
 ### A navigation check passes on the previous screen
 
 - **Signal:** intermittently, a wait right after the next tap times out even though the

package/skills/app-dev/android-development/references/setup.md

@@ -228,9 +228,11 @@ does not stop that server: use a verified private endpoint on a shared host and
 through the caller's owner. Capture the command's exit status, the final summary line and,
 when the journey failed, the `NATIVE_FAILURE` line and its `failure.json`.
 
-Expect every selected scenario's `PASS` marker, screenshots, and backend and Metro logs
-when the selected variant uses those services. Preserve the failed checkpoint's evidence
-before cleanup. A release build with embedded assets does not require Metro by default.
+Expect every selected scenario's result (`PASS` marker or the journey tool's report),
+required screenshots, and backend and Metro logs when the selected variant uses those
+services. For Maestro's result and screenshot rules, read [UI journeys](ui-journeys.md#evidence).
+Preserve the failed checkpoint's evidence before cleanup. A release build with embedded
+assets does not require Metro by default.
 
 ## Owned development session
 
@@ -385,8 +387,9 @@ For setup proof only. Record:
 - Each stage's exit status and duration.
 - The APK's SHA-256 (`shasum -a 256` or `sha256sum`) and its per-ABI `lib/` entries
   (`unzip -l`), checked on the APK itself rather than inferred from Gradle flags.
-- The journey's `PASS` markers and the cleanup results: database dropped, emulator exited,
-  container removed, no listeners left on the backend or Metro ports.
+- The journey's per-scenario results (`PASS` markers or the journey tool's report) and
+  cleanup results: database dropped, emulator exited, container removed, no listeners
+  left on the backend or Metro ports.
 - Earlier failed or incomplete attempts. A later pass does not erase them.
 
 State what the run does not prove: tablet, accessibility (TalkBack), physical devices,

package/skills/app-dev/android-development/references/ui-journeys.md

@@ -8,47 +8,113 @@ skill references it; it does not bundle or install it, and adding it is the repo
 | Situation | Recommendation |
 | --- | --- |
 | Repo has no UI journey tool | Offer Maestro for new single-device journeys. It replaces hand-written adb/UiAutomator launch, poll, capture and assertion code. |
-| Repo has a working harness | Keep the harness. Add Maestro flows for new journeys alongside it; do not migrate existing cases. |
+| Repo has a working harness | Reuse it when sufficient. Add Maestro only for a concrete benefit with repo authorization; an installed CLI alone is not a reason to add or migrate journeys. |
 | Coordinated multi-device case | Keep the custom harness. Maestro sharding runs independent flows, and a shard cannot depend on another. |
 
-## Device ownership
+Maestro changes the UI journey driver, not the [work loop or validation ladder](../SKILL.md#work-loop).
+Use focused flows at the applicable L0/L1 check, candidate-APK journeys at L2, and assigned
+acceptance journeys at L3. Source tests and required backend/native checks keep their roles.
 
-Run against the emulator the session owns and name it, so Maestro never starts or picks its
-own device:
+## Starting state and permissions
 
-```bash
-maestro --device "$ANDROID_SERIAL" test --test-output-dir "$LOG_DIR" ./maestro-flows
-```
+Declare each flow's intended starting app state and permissions in its YAML or owned
+fixture setup, and check included subflows and hooks for resets:
+
+- For a warm-runtime check, keep the running app or use `launchApp: {stopApp: false}`
+  to foreground it. Plain `launchApp` stops and relaunches the app by default, so it
+  cannot preserve the process whose state the check needs.
+- For restart, upgrade or fresh-install checks, use the checkpoint's required setup.
+  `clearState: true` and `clearState` clear Android app data; they do not install the
+  candidate APK or prove a fresh installation or upgrade. Clear only authorized disposable
+  state. If a reset removes debug endpoint preferences, restore them through the existing
+  owner and verify the app's actual code source before continuing.
+- Set permissions for permission-sensitive journeys. `launchApp` allows all permissions
+  by default; use the required denied or unset state to exercise denial or prompts.
+  An auto-granted run does not prove the permission-request journey.
+
+## Device ownership
+
+Run against the emulator the session owns and name it with `maestro --device <serial>`.
+Use the status handling under [Evidence](#evidence) inside the existing journey owner.
 
 Each session installs and starts Maestro's driver packages (`dev.mobile.maestro`,
 `dev.mobile.maestro.test`) through `am instrument`. That cost lands on the session's first
 flow, not on every step, so run every flow of the case in one session instead of one session
 per flow.
 
+Keep mutating checks exclusive on that device, including existing harness and Maestro
+runs. Reuse the existing runtime owner; Maestro is not a second emulator, backend or
+cleanup owner.
+
+If setup started a `setupUiAutomator` uiautomator2 process, have its owner verify ownership,
+stop it and wait for it to exit before starting Maestro; a live setup driver can block
+Maestro driver readiness. Restart that setup driver only after Maestro has fully exited,
+if it is still needed. Never stop a peer's process; coordinate with its owner instead.
+
+When comparing a custom journey adapter with Maestro, check scroll direction and prove
+offscreen targets with the [scroll-direction gotcha](gotchas.md#a-scroll-adapter-moves-away-from-the-target).
+
 ## Evidence
 
+Record the selected flows, executed assertions, run exit status, app/source identity and
+cleanup outcome. Accept the harness's `PASS` markers or Maestro's per-flow results/JUnit
+report as scenario results; a zero exit with no selected flows is not a pass. For JUnit,
+use `--format junit --output <owned-report-path>`; the report is separate from
+`--test-output-dir`. Capture successful checkpoints with `takeScreenshot` when the
+assignment requires visual evidence; normal passing flows have no automatic screenshots.
+
 `--test-output-dir` receives one session folder holding one self-contained folder per flow:
 `manifest.json`, `commands.json` (one entry per executed step), the failing step's
 `screenshots/` image and `screen-hierarchy/` JSON, and `logs/device-logcat.txt`. Convert that
 into the [device failure record](diagnosis.md#record-the-failed-device-case) instead of
 adding the journey helper:
 
+Give each case/attempt a new owned `LOG_DIR`, shared with its existing launcher so its
+partial-record fallback looks in the same directory. Retain earlier attempts separately;
+reusing a runtime does not mean reusing a failure-record destination. Confirm the pinned
+Maestro supports these flags and output layout before using the example.
+
+Run this body as the existing owner's journey command. Guard both commands so `set -e`
+cannot skip conversion or cleanup after a failure. The owner retains its bounded cleanup
+after the journey exits; this is not a new launcher or an acceptance checker.
+
 ```bash
-python3 <skill-base-dir>/scripts/maestro_failure.py --maestro-dir "$LOG_DIR/2026-07-31_173617" \
-  --evidence-dir "$LOG_DIR" --case "$DEVICE_CASE"
+maestro_status=0
+maestro --device "$ANDROID_SERIAL" test --test-output-dir "$LOG_DIR/maestro" \
+  --format junit --output "$LOG_DIR/report.xml" ./maestro-flows || maestro_status=$?
+conversion_status=0
+python3 <skill-base-dir>/scripts/maestro_failure.py --maestro-dir "$LOG_DIR/maestro" \
+  --evidence-dir "$LOG_DIR" --case "$DEVICE_CASE" || conversion_status=$?
+printf 'maestro_exit=%s conversion_exit=%s\n' "$maestro_status" "$conversion_status"
+if [ "$maestro_status" -ne 0 ]; then
+  exit "$maestro_status"
+fi
+exit "$conversion_status"
 ```
 
+Convert this invocation's finalized output before teardown. If startup or driver failure
+left no usable failed-step output, retain raw CLI logs and the original status and use
+the existing owner's partial-record fallback before cleanup. Conversion errors are
+evidence-processing failures, not replacements for the original test failure.
+
 It takes the session folder or one flow folder, writes `failure.json` into `--evidence-dir`
 (the flow folder by default) and prints the one `NATIVE_FAILURE` line for the first failed
 step. A passing flow writes nothing, and an existing record is never replaced. The artifact
 fields name the Maestro files (`screenshots/…`, `screen-hierarchy/…`, `logs/…`) rather than
 copying them into the adb names, so the failing frame and its hierarchy stay paired.
 
+Converter exit zero means processing completed, not that tests passed: a recorded failure
+also returns zero, and empty or incomplete step output may produce no record. Establish
+success from the executed assertions and per-flow results above, never from the converter
+or absence of `NATIVE_FAILURE`.
+
 ## Agents
 
 `maestro mcp` gives an agent `list_devices`, `inspect_screen`, `take_screenshot` and `run`.
-Explore the screen and draft a flow with it; the committed YAML flow is the proof, not the
-MCP session that found the selectors.
+Explore the screen and draft a repeatable YAML flow with it. Proof comes from executing
+the flow against the identified candidate with assertions that establish the claimed
+behavior and retained results. Committing YAML or finding selectors in MCP does not prove
+the journey passed.
 
 ## Limits
 
@@ -56,3 +122,9 @@ MCP session that found the selectors.
   on custom harness code.
 - Authentication codes still come from the harness's disposable database, passed into a flow
   with `maestro test -e` or resolved by its `runScript`; do not add a second fixture path.
+
+## Sources
+
+- [Launch state and permissions](https://docs.maestro.dev/reference/commands-available/launchapp)
+- [Android state clearing](https://docs.maestro.dev/reference/commands-available/clearstate)
+- [Reports and artifacts](https://docs.maestro.dev/maestro-flows/workspace-management/test-reports-and-artifacts)

package/skills/app-dev/app-debug/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: app-debug
 description: "Diagnose runtime failures in deployed Cloud Run services — 5xx/422 errors, tracebacks, Next.js SSR/hydration or Server Action failures, DB/Secret Manager connection errors, cold-start timeouts, container OOM. NOT for build or deploy failures (cloud-debug)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # App Debug

package/skills/app-dev/better-auth/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: better-auth
 description: "Add or debug Better Auth for Next.js App Router: login, sessions, protected routes, middleware, OAuth (including Feishu/Lark), cookies, Prisma, and Auth.js migration."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Better Auth for Next.js

package/skills/app-dev/data-catalog/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: data-catalog
 description: "Column definitions for warehouse tables, written inside the Spark/PySpark or SQL script that builds each table (CATALOG_TABLE / CATALOG_FIELDS, or a `-- @field` comment block), with a generated markdown catalog in docs/catalog/ and a CI check that fails a PR whose catalog is stale. Use when writing or changing a table script that adds, renames, removes, or changes the meaning of an output column or feature; when asked what a warehouse column or feature means; to set a repo up ('init the data catalog', 'generate the data dictionary', '字段字典', 'add catalog CI'); or to audit existing SQL or Spark scripts for undocumented columns. NOT for implementing or tuning the Spark job itself (pyspark), DAG wiring (airflow), or general workflow YAML (github-actions)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Data catalog

package/skills/app-dev/data-quality/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: data-quality
 description: "Check a published warehouse table's data against its data-catalog definitions with read-only SELECTs: columns never filled or stuck at one value, counts below zero, ratios outside 0–1, declared values that never appear and undeclared values that do. Then classify each finding as a wrong definition, wrong code, or wrong data. Use when asked whether a table's data is right, to profile or sanity-check a dwd/ads table, to find dead or constant columns, to check a column's values against its documented list, after a pipeline change ships, or when a data-catalog definition and the data might disagree. NOT for validating a Spark change before it ships (pyspark canary and reconciliation), writing definitions (data-catalog), or monitoring dashboards."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Data quality

package/skills/app-dev/ios-foundation/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ios-foundation
 description: "Set up and prove an Expo / React Native native iOS workspace from an assigned or fresh isolated workspace to a manual Login smoke on an owned iOS Simulator: isolated workspace and private caches, Xcode/runtime/CocoaPods preflight, frozen install with `pod install --deployment`, platform-scoped prebuild, an ad-hoc-signed Debug simulator build, a private simulator by exact UDID, Metro on a free port, a disposable PostgreSQL backend with owned cleanup, and the evidence record (setup proof only; feature work reports the smoke result). Use for 'set up iOS', 'build the iOS app', 'run the app on the iOS simulator', 'add iOS to the React Native app', 'prove the iOS build', or when a pod install, xcodebuild, simulator boot, Metro connection or Keychain session fails. NOT for Android (android-development), signing, TestFlight or App Store release, or general workflow YAML (github-actions)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # iOS foundation

package/skills/app-dev/monorepo/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: monorepo
 description: Turborepo architecture for shared packages, pnpm workspaces, DAL boundaries, and pipelines.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Turborepo Monorepo Architecture

package/skills/app-dev/nextjs-fullstack/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: nextjs-fullstack
 description: "Build or debug Next.js App Router features with React 19 — pages/layouts/route handlers, Server/Client Components, Server Actions, forms, middleware, DAL, strict TypeScript, Zod — plus our conventions: nuqs URL state, SWR cache, Skeleton/Progress + Sonner feedback, drag-and-drop upload, the portal app shell, list pages as filter/sort/paginate tables. shadcn component mechanics: see the shadcn skill."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Next.js 16 Fullstack Development

package/skills/app-dev/prisma-setup/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: prisma-setup
 description: Use when adding or debugging Prisma with PostgreSQL, Next.js, or Turborepo, including schema.prisma, prisma.config.ts, client generation, migrations, seeds, relations, adapters, and DAL/database-layer setup. Triggers on phrases like "Prisma schema", "prisma migrate", "schema.prisma", "seed the database", "PrismaClient error", "relation issue", or "database layer".
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Prisma v7 Setup Guide

package/skills/app-dev/pyspark/SKILL.md

@@ -12,7 +12,7 @@ description: >
   Connect, spark-submit, Hudi commits, backfills, validate-only canaries,
   cluster reconciliation, or Spark event-log profiling — including warehouse
   job timeouts, empty Hudi writes, or EMR/Dataproc performance regressions.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # PySpark

package/skills/app-dev/python-backend/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: python-backend
 description: "Python backend architecture for FastAPI, Tortoise ORM, Pydantic Settings, loguru, and uv. Also: uv.lock installs in CI/Docker via a proxy or mirror (`uv sync --frozen` bypasses it), slow uv installs on runners, relocking."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Python Backend Conventions

package/skills/app-dev/shadcn/SKILL.md

@@ -2,7 +2,7 @@
 name: shadcn
 description: "Add or debug shadcn/ui in a React/Next.js project: components.json, shadcn init/add, presets, registries, Tailwind styling, base/radix/aria composition, component fixes, and list-index pages — where the default is the DiceUI data table with filter/sort/pagination in the URL via nuqs, not a bare shadcn Table."
 allowed-tools: Bash(npx shadcn@latest *), Bash(pnpm dlx shadcn@latest *), Bash(bunx --bun shadcn@latest *)
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # shadcn/ui

package/skills/app-dev/zod-v4/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: zod-v4
 description: Zod v4 schema conventions and v3 migration for errors, validators, objects, enums, records, and async parsing.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Zod v3 to v4 Migration

package/skills/cicd/cloud-build/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: cloud-build
 description: "Build or debug Cloud Build pipelines for Cloud Run: cloudbuild.yaml, triggers, Artifact Registry, builds, migrations, deploys, secrets, VPC, notifications. Use cloud-deploy for staged promotion. NOT for GitHub Actions PR checks (github-actions)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Cloud Build Direct Deploy to Cloud Run

package/skills/cicd/cloud-debug/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: cloud-debug
 description: "Debug Cloud Build or Deploy failures: builds, deployments, health checks, and pipeline errors. Inputs: service, build ID, region. NOT for GitHub Actions runs (github-actions) or runtime errors in a running service (app-debug)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Cloud Build & Cloud Deploy Debug Skill

package/skills/cicd/cloud-deploy/SKILL.md

@@ -5,7 +5,7 @@ description: >
   CI/CD pipelines with staged promotion, verification gates, or GitFlow branching.
   Also use when debugging Cloud Deploy pipeline failures. NOT for simple single-container
   deploys — use cloud-build instead.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Cloud Deploy + Skaffold + Kustomize for Cloud Run

package/skills/cicd/docker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: docker
 description: Docker/Podman container architecture and build patterns. Read when designing or reviewing containerization, Dockerfile structure, multi-stage builds, PyPI mirror support, or docker-compose setup for Python/uv projects, and when a Dockerfile's dependency install misses the layer cache on every build (build args such as a commit SHA or version declared too early) or an image build is slow in CI.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Docker Build Patterns

package/skills/cicd/github-actions/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: github-actions
 description: "Author, review, audit, profile, optimize, or debug GitHub Actions workflows (.github/workflows/*.yml): run-history audits, job and step timing, resource bottlenecks, before/after comparisons, conditional CI by changed path, the one required gate check, PR and merge-queue lanes, sharding, workers, caching, self-hosted runners, timeouts, concurrency, permissions and action pinning, post-deploy verification, npm publishing. Use for 'set up CI', 'CI is slow', 'profile CI', 'optimize our pipeline', 'audit CI for redundant or wasted jobs', 'why is this check stuck expected or never started', 'harden this workflow', or 'browser not found on the runner'. NOT for pushing, opening, or merging a PR, or writing CI conventions into CONTRIBUTING.md (github-flow), queue rules or a check unmet inside Mergify (mergify), Playwright config and specs (e2e-test), cloudbuild.yaml or Cloud Run deploys (cloud-build), or which gates a repo must prove (ensure-coverage)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # GitHub Actions

package/skills/cicd/github-flow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: github-flow
 description: "Deliver a change after the commit: push, open a PR, wait for checks, and merge to main through the repo's flow (direct push, pull request, or merge queue). Use whenever you commit or finish a change, when CONTRIBUTING.md has a Delivery section, and for asks like 'commit this', 'push it', 'open a PR', 'ship it', 'land it', 'get it merged'. Also: declare a repo's delivery flow, or write the CI conventions and Delivery section into CONTRIBUTING.md on request. NOT for writing workflow YAML (github-actions), Mergify config or a stuck queued PR (mergify), cutting a release (resolve-release), or PRs that resolve-issues or rush-issues deliver."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # GitHub Flow

package/skills/cicd/google-cloud/SKILL.md

@@ -5,7 +5,7 @@ description: >
   project management. Use when configuring GCP resources, managing service
   accounts, setting up IAP access, configuring VPC networks, managing secrets,
   or debugging cloud infrastructure.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Google Cloud Platform (GCP) Skill

package/skills/cicd/mergify/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: mergify
 description: "Mergify merge queue and stacked PRs (`mergify stack`): config, rules, queue status, delivery. Use whenever a merge queue or stack is involved, including plain asks ('watch #123 till it merges', 'where is #412 in the queue', 'push this stack'): `gh pr view`/`gh pr checks` cannot see a dequeue; use `mergify queue show` and the bundled watcher. Also: a hook saying 'use mergify stack push', a missing Change-Id; authoring or debugging `.mergify.yml`, queue rules, merge protections, batch size, the ruleset making merges queue-only; enqueue policy (`@mergifyio queue` vs `auto_merge_conditions`); a push dequeuing a queued PR; bypass actors; freezing a branch. Failures: a PR stuck, queued but never merging, or merged unqueued; CI green on GitHub but unmet in Mergify; a batch going red or bisecting; a queue check missing rather than failing. Outranks the vendor mergify-* skills. NOT for pushing a PR in a repo without stack hooks (github-flow), workflow YAML (github-actions), or GCP deploy pipelines (cloud-deploy)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Mergify Merge Queue

package/skills/cicd/podman/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: podman
 description: "Debug, design, or fix Podman: rootless/rootful containers, pods, podman-compose, the socket and systemd services, Docker-compatible API (DOCKER_HOST/CONTAINER_HOST), networking, volumes, SELinux labels, Docker migration, and CI/SSH provisioning of rootless sockets (user lingering, XDG_RUNTIME_DIR). Covers FailedToOpenSocket and systemctl --user DBUS/XDG errors."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Podman Operations

package/skills/content/article-review/SKILL.md

@@ -6,7 +6,7 @@ description: >
   Use when a user shares an article, pastes article text, sends a URL, or asks to
   review, rate, critique, evaluate, 评价, 点评, 分析, or 看看 any article, post, or 文章.
   Default template is 公众号-支付行业.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # 文章评审引擎

package/skills/content/article-to-image/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: article-to-image
 description: "Generate article cover images: WeChat banner/square (公众号封面), Xiaohongshu (小红书封面), LinkedIn banner, general wide. Brainstorms 4 visual directions from the article, then renders each format with correct aspect ratios and title-safe zones. Use when given an article and asked for covers, banners, or 出图."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Article-to-Image

package/skills/content/flowchart-svg/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: flowchart-svg
 description: Create polished flowcharts directly as SVG and export PNG copies. Use when asked to draw, design, render, or deliver process diagrams, architecture diagrams, consulting workflows, decision flows, swimlanes, or other flowcharts as image files, especially when final outputs must include .svg and .png versions.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Flowchart SVG

package/skills/content/image-gen/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: image-gen
 description: Generate an image from a text prompt with OpenAI gpt-image-2 or Google Nano Banana (Gemini), saved to an image file. Use whenever the user asks to generate, create, make, draw, paint, render, or design an image, picture, illustration, photo, artwork, logo, icon, avatar, banner, hero image, thumbnail, poster, wallpaper, sticker, or concept art — including phrasings like "an image of X", "a picture of X", "show me what X would look like", or a request for a visual for a slide, blog post, README, or social post. Also triggers on Chinese phrasings such as 生成图片, 画一张图, 做一张海报, 设计一个 logo. NOT for charts or data visualizations (dataviz), flowcharts or architecture diagrams (flowchart-svg), or editing an existing image file.
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Image Generation

package/skills/content/mermaid/SKILL.md

@@ -2,7 +2,7 @@
 name: mermaid
 description: Create and edit Mermaid diagrams for architecture, API flows, database schemas, workflows, and data models.
 user-invocable: true
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Mermaid Diagram Creation

package/skills/content/wechat-article-writer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: wechat-article-writer
 description: "Write WeChat 公众号 articles in Chinese content styles — 踩坑型 (pitfall-story), 实操型 (how-to), 对比型 (comparison), 观察型 (industry insight) — in the account's house style from the nearest WRITING.md. Use for drafting from scratch, rewriting a draft, adapting source material into a publishable article, or picking the right style. NOT for business or technical documents (write-doc)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # WeChat Article Writer (公众号写作)

package/skills/content/wechat-publisher/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: wechat-publisher
 description: "Publish articles to a WeChat Official Account (公众号) via API: push Markdown to the draft box (or auto-publish with --publish), convert Markdown to WeChat HTML, upload images to the media library. Requires AppID + AppSecret + whitelisted server IP on a 认证订阅号/服务号. Consumes wechat-article-writer's Markdown."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # WeChat Publisher (公众号发布)

package/skills/content/wechat-search/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: wechat-search
 description: "Search WeChat 公众号 articles via Sogou Weixin, or read/summarize an article from a mp.weixin.qq.com URL (读/分析/总结) — suggest proactively when such a URL appears. Use for Chinese WeChat content, industry reports, competitor or trending topics. Requires Chrome Browser Relay. NOT general web search (web_search)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # WeChat Article Search & Reader (搜狗微信搜索)

package/skills/content/xai-search/SKILL.md

@@ -9,7 +9,7 @@ metadata:
         type: secret
         required: true
         description: API key for direct xAI or the explicitly configured Responses gateway
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # xAI Search (X/Twitter + Web)

package/skills/core/distill-writing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: distill-writing
 description: "Learn a house writing style from approved sample documents, or save an explicitly stated project document preference, into WRITING.md and writing/templates/. Use for sample-based style learning, house-style setup or refresh, and requests such as 'remember this for future PRDs' or 'make this our report default', including handoffs from write-doc, write-report or plain-language. Preserve manual edits and separate document types. NOT for drafting a document (write-doc) or analytical report (write-report) or saving chat-only preferences (plain-language)."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Distill a writing style

package/skills/core/doc-to-md/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: doc-to-md
 description: "Convert documents (PDF, DOCX, PPTX, XLSX, images) to Markdown so agents can read them. Use as the preprocessing step whenever binary files need to enter agent context — contract review, compliance audit, document analysis, evidence review."
-release-version: 0.48.0
+release-version: 0.48.1
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # doc-to-md