Update to Prisma

{
  "description": "Save a Prisma Composer app to GitHub, connect its existing Prisma project, and enable or diagnose default-branch automatic deployments. Use when the user accepts the offer to save their code to GitHub and connect it to Prisma for automatic updates, accepts the shorter GitHub-saving offer, or directly requests this setup, including resuming an interrupted connection. Do not start GitHub setup for an ordinary build/deploy request, unrelated Git work, or a request to deploy an app before a live target has been established.",
  "included_files": [
    {
      "relative_path": "references/github-deploy.md",
      "size_in_bytes": 9531
    }
  ],
  "name": "prisma-github-deploy",
  "skill_md_contents": "---\nname: prisma-github-deploy\ndescription: >-\n  Save a Prisma Composer app to GitHub, connect its existing Prisma project,\n  and enable or diagnose default-branch automatic deployments. Use when\n  the user accepts the offer to save their code to GitHub and connect it to Prisma\n  for automatic updates, accepts the shorter GitHub-saving offer, or\n  directly requests this setup, including resuming an interrupted connection.\n  Do not start GitHub setup for an ordinary build/deploy request, unrelated Git\n  work, or a request to deploy an app before a live target has been established.\n---\n\n# Save to GitHub and enable automatic updates\n\nTake a working Composer app with a verified Prisma deployment through repository\nsaving, project connection, and verified GitHub deployments. Use the existing\n[build-and-deploy workflow](../prisma-build-and-deploy/SKILL.md) for local setup,\nauthentication, and application verification, and its Composer reference for APIs.\nRead [GitHub deployment details](references/github-deploy.md) before configuring CI.\nFor automatic deployments, establish a missing live target through that journey\nfirst. A save-only request needs no cloud deployment or Prisma connection.\nDo not add unrelated PR-management or migration work.\n\nAccepting the build workflow's combined offer authorizes saving, connection, and\nautomatic-update setup. Honor an explicit save-only or no-deploy request: save\nthe source and finish without connecting or enabling deployments. Do not turn\nsetup into a branch-preview demonstration or invent an application change.\n\nThe agent works locally in the desktop app; GitHub Actions executes the resulting\nworkflow remotely. Browser/cloud agent execution remains unsupported. Handle\ncommands and supported authentication yourself. The user completes browser consent\nwhen required, without terminal commands, pasted tokens, or credential copying.\n\nDo not access or upload PHI or PCI-regulated payment card data, including project\nfiles, databases, and logs. If context suggests it is present, stop before access,\nclarify without requesting real examples, and offer a separate synthetic-data\nenvironment. If encountered unexpectedly, stop and do not reproduce it. Never\nswitch from MCP to CLI or GitHub to bypass the restriction. Ordinary Todo apps\nneed no extra questionnaire. Preserve secret redaction during diagnostics.\n\n## Establish the same app and save its code\n\n- Inspect Git state, remotes, package manifest, lockfile, Composer configuration,\n  and existing workflows. Preserve the user's uncommitted work and app conventions.\n  For automatic updates, confirm the authenticated Prisma workspace and deployed\n  project by ID, production/default versus named target, actual live branch,\n  region, service/database IDs, and both verified app/project links; retain a\n  non-sensitive persistence sample for verification.\n  Resolve ambiguity before pushing or connecting; never infer identity from a\n  matching display name alone.\n- Reuse an appropriate existing repository. Otherwise propose an app-derived\n  name, default to private visibility, and confirm owner/destination unless already\n  specified. New repositories use `main` as the default branch; preserve an\n  existing repository's default branch. Check access and contents before pushing. Never\n  replace a remote, force-push, or overwrite repository contents to resolve a conflict.\n- Save source, Composer configuration, and the lockfile. Review the exact staged\n  files and diff first; exclude secrets, local auth, deployment state/reports, logs,\n  and private test instructions. Do not commit an entire directory blindly.\n  Record the repository and known workspace/project IDs, target kind and branch,\n  region, verified app/project links,\n  and deployment behavior in existing app documentation, without credentials or\n  machine-specific paths. Keep dependency/runtime pins. For save-only requests,\n  finish here without connecting, adding automation, or triggering a workflow;\n  clarify before pushing if saving to that branch would itself deploy.\n\n## Connect the existing Prisma project\n\nCheck its current repository connection through a supported platform read or\nConsole. An already-correct connection is reusable. A different connection or a\nrepository linked elsewhere is a conflict to clarify, not permission to disconnect\nit or create another project. Connect with the explicit project ID using the CLI\nin the reference, then verify the repository identity and project mapping before\nenabling automation.\n\nGitHub authorization to save code and the Prisma GitHub App's repository access\nare separate. Explain whichever connection is missing in plain language. Keep a\nmanaged interactive connection attempt alive during browser authorization; do not\nclaim success from the browser alone. On interruption, inspect completed steps and\nresume with the same repository/project. Do not restart by provisioning replacements.\n\n## Enable and verify deployment automation\n\nAdapt the reference's workflow using `prisma/cloud-deploy-action@v1.7.0`, GitHub\nOIDC, and compatible Node/Bun runtimes. Preserve existing install/build conventions;\ninspect other workflows to avoid duplicate deployments. For new automation,\ndeploy pushes only to the repository's actual default branch. For a verified\nproduction/default target, omit the action's stage input; do not set `stage: main`.\nFor an existing named stage such as `demo`, retain its explicit stage mapping.\nSerialize runs per target. Never relocate existing resources to match a branch\nname. Preserve appropriate\nexisting workflows, including their previews; do not replace them just to match\nthe example. A green `skipped-no-credential` run means setup is incomplete.\n\nVerify the deployment triggered by committing the workflow, leaving application\nbehavior unchanged. Match its commit and successful outcome to the same live\nresources and preserved sample data. A successful no-op is valid when the deployed\napp already matches that commit; do not manufacture a feature or new version to\nprove an update. If setup is already complete, reuse matching successful-run\nevidence and check the current app instead of creating another deployment.\n\nConfirm the workflow's commit, deployment/build result, live service version, URL,\ndatabase-backed behavior, and browser result before saying automation is ready.\nFollow the shared [verification and recovery guidance](../prisma-build-and-deploy/references/toolchain.md#verification-and-live-recovery)\nand the app's existing persistence checks. Report partial progress and a specific\nfailing step for denied access, missing OIDC credentials, quota, build, or startup\nfailures. Preserve connections and state while fixing the cause; no automatic\ndestructive recovery.\nOptional MCP diagnostics follow the existing workflow's identity and data-use rules.\n\nFinish with repository and successful workflow-run links, **Open your app**, and\n**Manage your Prisma project**, retaining the verified deployment links and branch.\nExplain that\ndefault-branch updates deploy automatically and state any incomplete checks. For\nsave-only requests, report only the saved repository. Finish setup here: do not\nadd demonstration features, PRs, extra preview pushes, merges, or branch cleanup.\n"
}