powerplatform-core

Discover Dataverse repository context and plan source-controlled changes.

17|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/satriotsubasa/PowerPlatform-Core --skill powerplatform-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: powerplatform-core
Source: https://github.com/satriotsubasa/PowerPlatform-Core/tree/main
Command: npx skills add https://github.com/satriotsubasa/PowerPlatform-Core --skill powerplatform-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires powerplatform_common, power_automate_common, yaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

PowerPlatform-Core enables Codex to read a repository, understand model-driven app and solution structure, and safely plan and deliver repository-driven changes for Microsoft Power Platform and Dataverse development.

Core Features & Use Cases

  • Repo context discovery and surface selection (code, metadata, PCF, flows, or solution ALM).
  • Deterministic, repo-backed changes with live mutation preflight and guarded deployment.
  • Guided execution across layered, unpacked, ambiguous, or sparse repos, without assuming a single house structure.

Quick Start

Install this skill and begin triaging a repo by running python scripts/discover_context.py --path .

Frequently Asked Questions about powerplatform-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Dataverse solution deployment from a repository?

Automate Dataverse solution deployment by reading the repository, inferring the solution structure, and routing changes through deterministic, surface-specific deployment paths after a mandatory preflight gate.

What is repo-first Power Platform development?

Repo-first Power Platform development is planning source-controlled changes by reading a repository, selecting the appropriate surface (code, metadata, PCF, flow, or solution ALM), and executing safe deployments.

Can I manage Power Automate flows using a source-controlled repository?

Yes, you can manage flows by letting the tool infer the solution structure from your repository and selecting the flow surface for targeted, source-controlled changes.

How do I plan safe changes across an unpacked Dataverse solution repository?

Plan safe changes by running context discovery on the unpacked repository, selecting the correct surface, and enforcing a preflight gate before any live mutation occurs.

Does this approach work with sparse or ambiguous Power Platform repositories?

Yes, it provides guided execution across layered, unpacked, ambiguous, or sparse repositories without assuming a single house structure, selecting the appropriate surface for each task.

Why is a preflight gate required before live mutations in Dataverse?

A preflight gate is required before live mutations to ensure changes are deterministic and safe, preventing unvalidated repository modifications from directly impacting the target Dataverse environment.