菜单
Cut a PPDS Skills package release — get the recapture, decide the version bump, clean up prose, update CHANGELOG, tag + GitHub Release. Use when PPDS ships a new stable CLI/MCP that the skills package must track, or to publish any skills-package version bump.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Install, authenticate, and safely operate the Power Platform Developer Suite (PPDS) CLI and MCP server against Microsoft Dataverse — auth profiles, environment selection, the environment-safety model, and error interpretation. Use when the user wants to connect to Dataverse with PPDS, set up `ppds` or `ppds-mcp-server`, manage auth profiles or environments, decide between the PPDS CLI and MCP surfaces, or interpret a PPDS error or exit code. Load this skill first before any other ppds-* skill.
Bulk Dataverse data operations with PPDS — schema-driven export/import (CMT-compatible), direct environment-to-environment copy, CSV load, bulk update/delete, truncate, user mapping, and dependency analysis. Use when the user wants to move records between environments, seed reference data, export data to a ZIP, load a CSV into a table, bulk-delete records, or migrate data with lookup and owner remapping. Read ppds-core first for auth and safety rules.
Browse and author Dataverse schema with PPDS — list entities/tables, inspect attributes/columns and relationships, create or update tables, columns, relationships, alternate keys, and global choices/option sets, compare schemas across environments, and adjust views and forms. Use when the user wants to know what columns or relationships an entity has, create or modify a table or column, manage option sets or keys, diff schema between environments, or edit a view or form definition. Read ppds-core first for auth and safety rules.
Register, deploy, and debug Dataverse plugins declaratively with PPDS — attribute-driven registration ([PluginStep]/[PluginImage]/[CustomApi]), the extract → diff → deploy loop, assembly management, Custom APIs, service endpoints, and plugin trace log debugging (list/get/timeline). Use when the user wants to register or deploy a plugin assembly, sync plugin steps from code, diagnose a plugin error or performance problem, read plugin trace logs, or manage Custom APIs. Read ppds-core first for auth and safety rules.
Query and modify Microsoft Dataverse data with PPDS — SQL (transpiled to FetchXML) with joins, CTEs, aggregates and window functions, raw FetchXML, guarded DML, execution plans, TDS endpoint routing, and query history. Use when the user wants to read, filter, join, aggregate, count, or analyze Dataverse records, run INSERT/UPDATE/DELETE statements, inspect a query plan, convert SQL to FetchXML, or recall a previous query. Read ppds-core first for auth and safety rules.
Dataverse solution ALM with PPDS — export/import solutions, watch import jobs, inspect components, manage environment variables and connection references, and generate/sync/validate deployment settings files for target environments. Use when the user wants to export or import a solution, move customizations between environments, check why a solution import failed, fix orphaned connection references, set environment variables, or prepare deployment settings for a pipeline. Read ppds-core first for auth and safety rules.
| name | release |
| description | Cut a PPDS Skills package release — get the recapture, decide the version bump, clean up prose, update CHANGELOG, tag + GitHub Release. Use when PPDS ships a new stable CLI/MCP that the skills package must track, or to publish any skills-package version bump. |
No NuGet/npm pipeline — users install from the repo / plugin marketplace, so a
"release" is a reviewed version bump on main plus a tag and GitHub Release. The
recapture is automated; this skill covers the judgment + finalization left to a
human.
release skill §8 dispatches the recapture automatically), orPreferred — let the automation produce the PR:
gh workflow run recapture-on-release.yml
It installs the released CLI/MCP, regenerates captured-help/ + references, bumps
the frontmatter pins, runs the gate, and opens a PR. Gotchas: the Allow
GitHub Actions to create and approve PRs repo setting must be on, and a
bot-opened PR shows no CI — close/reopen it to fire skill-evals.
Offline alternative: dotnet tool update -g PPDS.Cli && dotnet tool update -g PPDS.Mcp
then python3 tools/recapture.py. See CONTRIBUTING "Regenerating the references".
Diff captured-help/ against the previous tag. Per the package's semver
(plugin.json / marketplace.json):
rc → stable).check_skills.py::check_prose_version_drift early-returns on a stable pin, so
hand-check these when moving rc → stable:
--prerelease install guidance and stale rc mentions in README.md,
DESIGN.md, skills/*/SKILL.md, and hand-written skills/*/references/*.md.CHANGELOG.md (immutable history) and CONTRIBUTING.md
(intentionally version-agnostic runbook guidance).serverInfo.version (which can lag the NuGet
package), so bump ppds_mcp_version_tested only if that value changed.version in .claude-plugin/plugin.json and the marketplace.json
plugin entry — the eval enforces they match.CHANGELOG.md entry (Keep a Changelog sections) and the [X.Y.Z]
release-link footer.python3 evals/check_skills.py # must pass: validates against the new capture
Open the PR, link/close the tracking issue (e.g. Closes #N), resolve any review
threads (conversation resolution is required to merge). Squash-merge.
git checkout main && git pull # main now at the squash-merged release
git tag -a vX.Y.Z -m "release: X.Y.Z"
git push origin vX.Y.Z
gh release create vX.Y.Z --title "vX.Y.Z" --notes "<the CHANGELOG X.Y.Z section>"
CONTRIBUTING.md — "Regenerating the references" + "Release process"..github/workflows/recapture-on-release.yml — the recapture automation.release skill §8 — what triggers our recapture on a PPDS stable.