deploy
Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.1k
- Forks
- 232
01 前言 Front Matter
- name
- deploy
- model
- sonnet
- description
- Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or pushing updates.
- allowed-tools
- Read, Edit, Write, Grep, Glob, Bash
- user-invocable
- true
03 SKILL.md 正文
? Shared Instructions: shared-instructions.md - Cross-cutting concerns.
Deploy
Builds and deploys the app in the current directory to Power Platform.
Workflow
- Check Memory Bank → 2. Build → 3. Deploy → 4. Update Memory Bank
Step 1: Check Memory Bank
Check for memory-bank.md in the project root. If found, read it for the project name and environment. If not found, proceed — the project may have been created without the plugin.
Step 2: Build
npm run build
If the build fails:
- TS6133 (unused import): Remove the unused import and retry.
- Other TypeScript errors: Report the error with the file and line number and stop. Do not deploy a broken build.
Verify dist/ exists with index.html before continuing.
Step 3: Deploy
Ask the user: "Ready to deploy to [environment name]? This will update the live app." Wait for explicit confirmation before proceeding.
Resolve the CLI first (see cli-binary.md): run as
$PA app push(npx --no-install pa …), never a barepa. Onpower-apps-only projects, translate topower-apps push.
pa app push
Capture the app URL from the output if present.
If deploy fails, report the error and stop — do not retry silently. Common fixes:
- Auth error / token expired →
pa auth logout(orpower-apps logoutonpower-apps-only projects), then retry — the CLI will re-prompt browser login. - Environment mismatch → update
environmentIdinpower.config.jsonto the correct value and retry.
Step 4: Update Memory Bank
If memory-bank.md exists, update:
- Last deployed timestamp
- App URL (if captured)
04 同仓库更多 Skills
compare-site-configurations
Compare Power Pages site configurations between two environments, such as dev, test and production, or between a local download and the live site, and explain which differences change site behavior. Use when a site works in one environment but not another (for example, works in dev but fails in test), to check configuration drift before promoting or deploying, or to see what changed between two sites. Produces a shareable HTML report and a JSON file that VS Code can import.
setup
Use when Process Intelligence needs building, explicit cloud/account/environment configuration, sign-in, connection diagnostics, or recovery from an authentication error.
report-issue
Use when the user wants a Process Intelligence bug-report draft or support summary for a failed operation.
investigate-process
Use when a broad Process Mining business question, observed pattern or competing explanation needs investigation across analytical perspectives.
derive-metric
Use when a requested measure is missing, a saved custom metric needs reuse, or an ephemeral formula or derived scalar is needed.
compare-cohorts
Use when comparing process cohorts, departments, periods or before-and-after results under matched definitions.