@1aboveio/skills 1.0.20 → 1.0.22

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@1aboveio/skills",
-  "version": "1.0.20",
+  "version": "1.0.22",
   "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": "b5727bb217684e6aaec8d47959a652a8c7cda115b14286773169598a2857d6de",
-    "releaseIdentity": "b6b2b1b7349f7aa497291f7eb63119c5c0839e26fbf79753451579d695b846d5"
+    "metadataDigest": "03e5e1c1f64703da55ed571aba131e0267861b3d60acce3b27b6ad0ad03a4a92",
+    "releaseIdentity": "7f91927caca33de3dd3073b7fdf503226be323220884dc30086650e6a6bb07e1"
   },
   "pi": {
     "skills": [
@@ -261,7 +261,7 @@
         ]
       }
     ],
-    "digest": "760a1d385aebb37474f1ec980972c8a5760db4d096978322a608e5a7fa8cbac7"
+    "digest": "f05d73f9747c37b855d59bab4cf5cb4e412506ec630b5c9662064f2554a41339"
   },
   "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.50.0
+release-version: 0.50.2
 ---
 **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, native 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. Maestro journey authoring, UI-driver migration and flow diagnosis belong to maestro. 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.50.0
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Android development

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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # iOS foundation

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

@@ -1,7 +1,7 @@
 ---
 name: maestro
 description: "Design, run, debug and migrate mobile E2E journeys with Maestro: complete flows and subflows, selectors, parameters, exclusive UI-driver ownership, non-UI authentication/backend helpers and failure evidence. Use for Maestro YAML/CLI/MCP work, slow fragmented mobile journeys, UiAutomation driver collisions, or replacing a hybrid Python/uiautomator2 UI harness. Android-first; use platform-neutral flow guidance for iOS only with its verified device/runtime contract. NOT for Android provisioning/builds (android-development), iOS setup (ios-foundation), browser Playwright tests (e2e-test), or CI workflow YAML (github-actions)."
-release-version: 0.50.0
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # Maestro
@@ -26,6 +26,13 @@ the assignment and survives context reload, not as a saved policy change.
 
 ## Work loop
 
+When an issue has Acceptance Criteria needing mobile UI proof, implement or reuse
+flows whose assertions cover those criteria. Keep case selection runnable through
+the maintained local and CI callers with isolated fixtures and failure artifacts.
+Workers run focused development checks; CI qualifies automated acceptance on the
+identified candidate app. Return with CI pending when appropriate; manual and
+physical-device criteria remain explicit obligations at their assigned gate.
+
 1. **Select proof.** Name the user journey and its required observations. Map each to a
    UI assertion, non-UI helper or specifically justified native case using
    [the test split](references/journeys.md#split-by-responsibility). Reuse sufficient

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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **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.50.0
+release-version: 0.50.2
 ---
 **Updates:** Once/session run `node <skill-base-dir>/release-check.mjs`.
 # GitHub Actions
@@ -43,7 +43,9 @@ replacement of an established pipeline during an audit or performance-only chang
 7. **Add post-deploy and scheduled lanes** if the repo deploys or publishes.
    → [post-deploy-and-publishing.md](references/post-deploy-and-publishing.md)
 8. **Verify**: `actionlint`; one PR per area runs only that area's jobs; timings meet the SLA.
-   Failures → [debugging.md](references/debugging.md)
+   Failures → [debugging.md](references/debugging.md). Waiting on a live run, or on a publish
+   run → [debugging.md#watching-a-run](references/debugging.md#watching-a-run): `scripts/watch-run.mjs`
+   reports job/step transitions and slow steps, which `gh run watch`'s 30-second repaint hides.
 
 ## Principles
 
@@ -88,6 +90,10 @@ replacement of an established pipeline during an audit or performance-only chang
 - Fail on a missing secret.
 
 **Lanes**
+- When issues include Acceptance Criteria, wire their automated tests into the
+  appropriate candidate lane and expose their results through the existing gate.
+  See [acceptance execution](references/pipeline.md#acceptance-execution); preserve
+  required check names and obtain authorization for changes to merge requirements.
 - Test the deployed revision after deploy, never a local build.
 - Alert on every scheduled or non-PR failure.
 - Never let an AI review be the only gate, or auto-pass it on timeout.

package/skills/cicd/github-actions/references/debugging.md

@@ -11,3 +11,24 @@
 - Queue/dequeue questions → `mergify` skill; `gh pr checks` can't see a dequeue.
 - Validate locally: `actionlint` for syntax and expression mistakes; `act` for simple jobs
   (not for self-hosted or service-container jobs).
+
+## Watching a run
+
+`gh run watch` repaints a status block and an elapsed clock every 30 seconds, and that repaint
+is not progress: a job wedged in one step reads exactly like a job moving, while the step names
+are what scrolls out of view. Watch with the bounded CLI instead:
+
+```bash
+node "$SKILL_DIR/scripts/watch-run.mjs" --run <id> [--repo owner/repo]
+```
+
+It reads `gh run view --json status,conclusion,jobs` on an interval and writes one record only
+when the run's state changes, naming the job/step transitions that caused it (`changes`). A job
+or step past `--slow-step-minutes` is warned about once **while it is still running**, with its
+duration and URL. The exit code is the verdict: 0 green; 4 names the failed job and its failed
+steps, or `STALLED` with `reason: no-progress` naming the jobs nothing has started, or
+`UNKNOWN` when the provider stays unreadable — an unreadable read is no information, never a
+red run.
+
+For a finished run's full job/step profile, that is the other tool:
+`scripts/ci-run-audit.mjs --profile-run <id>`.

package/skills/cicd/github-actions/references/pipeline.md

@@ -29,6 +29,32 @@ rc tag ───────────► Cloud Build: prod candidate at 0% tr
   → [post-deploy-and-publishing.md](post-deploy-and-publishing.md)
 - **Scheduled lanes:** alert on failure (issue or chat ping).
 
+## Acceptance execution
+
+Execute the tests that prove the issue's Acceptance Criteria in the lane that can
+qualify them: change-scoped PR checks, combined-tree queue checks, or checks against
+the deployed revision. Without a queue, put pre-merge acceptance on the up-to-date PR.
+Workers author tests and run focused development checks; CI supplies the qualifying
+automated result. Keep human judgment and physical-device checks explicit at their
+assigned gate rather than treating automation as proof of those claims.
+
+For acceptance suites that consume a build, build once for that candidate and fan
+out independent suites against the same artifact. Bind results to the candidate SHA
+and artifact identity; post-deploy tests verify the serving revision. Rebuild only
+when a suite requires a different build configuration. Use isolated fixtures and
+slot-sized parallelism, and retain useful failure logs, traces or device artifacts.
+
+Aggregate each suite into its assigned gate: pre-merge acceptance into the PR/queue
+gate, deployed acceptance into the post-deploy or promotion gate. A later-stage suite
+does not block an earlier stage unless the agreed contract requires it.
+Missing results, unexpected
+skips and failures cannot pass it. Select checks by their affected inputs and required
+combined-tree coverage; acceptance does not imply a full matrix on every push.
+If execution or enforcement is missing, implement the authorized workflow work and
+surface any separate merge-rule change for approval. A green unrelated job does not
+satisfy the issue. Generate a requested checklist from test results rather than having
+agents reconstruct a campaign by hand.
+
 ## Merge queue: optional, pick one
 
 | Option | When | Wire |

package/skills/cicd/github-actions/references/post-deploy-and-publishing.md

@@ -31,3 +31,10 @@ npm packages: trusted publishing (OIDC, no token): `environment: npm-publish`,
 already published? then assert its provenance matches this commit), a pack-contents check,
 publish, poll the registry until visible, then create the tag and release idempotently.
 Restrict to the default branch; pin the npm version; keep `contents: write` off the install step.
+
+**The registry is the verdict, not the run.** A green publish workflow proves the job exited 0;
+the published version is what the registry reports. Wait on the artifact (`npm view
+<pkg>@<version> version`), and read the run for diagnosis with `scripts/watch-run.mjs` — its
+job/step transitions and slow-step warnings are the useful signal, while a repainted status
+line is not. A run that fails after the version appears is a hand-back naming what already
+shipped; a version that never appears is not a success however green the run was.