fix: update terraform docs for provider-docs and provider-test-patterns skills - #83
Open
AdamTylerLynch wants to merge 1 commit into
Open
Conversation
This was referenced Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repo listings drifted out of date as skills were added:
terraform/README.md—provider-docswas missing from theterraform-provider-development table, the
npx skills addlist, and the structuretree
AGENTS.md— bothprovider-docsandprovider-test-patternswere missing fromthe structure tree, the plugin-contents table, and the
npx skills addlistCHANGELOG.md— neither skill had an entry; both added under Unreleased/Added(the 0.1.0 "9 total skills" line was accurate at the time and is left alone)
Docs-only change; no skill content touched. Deliberately does not mention the new
provider-configurationskill — its own PR self-registers, keeping both PRs correctin any merge order (expect a trivial adjacent-line conflict in these three files with
that PR; both-sides-keep resolves it).
Verification:
scripts/validate-structure.shpasses.