with one click
check-sync-provider
// Checks if the downstream provider repository is aligned with the correct Magic Modules base commit.
// Checks if the downstream provider repository is aligned with the correct Magic Modules base commit.
Plan a remediation strategy after a test failure.
Executes code generation from Magic Modules into downstream Terraform providers and optionally compiles the binary.
Triggers the QA Test Runner subagent to reproduce failures and interpret logs.
Checks sync status and invokes the subagent to align repositories if needed.
Gather context on a change or bug and plan the implementation.
Configures Terraform CLI with developer overrides to test locally built provider binaries without full Go acceptance tests, enabling rapid plan/apply cycles.
| name | check-sync-provider |
| description | Checks if the downstream provider repository is aligned with the correct Magic Modules base commit. |
check-sync-providerUse this skill to verify if the downstream repository is at the correct baseline commit before generating code or running tests.
GoogleCloudPlatform/magic-modules remote (usually upstream).main: Use current commit (HEAD).git merge-base HEAD <canonical-remote>/main to find where the branch diverged.HEAD of the downstream repository matches that found commit.