Burythehammer Claude Code Plugins
burythehammer-claude-code-plugins is a Claude Code plugin for the Build phase that supports Terraform provider development with migration, schema, and workflow-oriented skills.
by burythehammer · github.com/burythehammer/claude-code-plugins
Guide Claude through Terraform provider schema design, migrations, and step-by-step provider workflows when you maintain or fork a custom provider.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install burythehammer-claude-code-plugins@burythehammer/claude-code-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:burythehammer/claude-code-plugins") and the paste-ready config with skillselion.get_install_config("plugin:burythehammer/claude-code-plugins").
What it does
burythehammer-claude-code-plugins is a compact Claude Code plugin collection aimed at engineers who build or maintain Terraform providers—not operators who only consume modules. The catalog lists one plugin whose keywords emphasize migration, schema mapping, provider patterns, gotchas, and a step-by-step workflow, which suggests the agent is steered through the repetitive, error-prone parts of provider authoring rather than one-click deploys. Solo maintainers of niche providers, contributors upstreaming resources, and indie infra tool builders benefit when Claude already knows Terraform plugin framework conventions and can flag mapping mistakes before a release. Use it while defining resources and data sources, refactoring SDK versions, or documenting breaking schema changes. It is specialized DevOps tooling: high leverage if your product exposes cloud APIs through Terraform, and skippable if you only apply modules written by others.
Highlights
- Single-plugin collection focused on HashiCorp Terraform provider development
- Step-by-step workflow and migration-oriented guidance from catalog keywords
- Schema mapping, common patterns, and gotchas called out for provider authors
- Framework-level skills for moving or migrating provider implementations
- DevOps-oriented taxonomy alignment (development category in source metadata)
Why builders use it
Maintaining a Terraform provider means wrestling with framework migrations, schema drift, and undocumented gotchas that slow solo authors and invite breaking releases.
After registration, Claude can follow provider-centric workflows—mapping, migration steps, and pattern checks—so you ship provider changes with fewer schema surprises.
At a glance
- Type - Plugin in DevOps.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is burythehammer-claude-code-plugins for?
It is for Terraform provider maintainers and contributors who need Claude Code skills tuned to schema design, migrations, and provider framework workflows.
When should I use burythehammer-claude-code-plugins?
Use it while implementing or refactoring provider resources, planning SDK migrations, or reviewing provider PRs for mapping and breaking-change risk.
How do I add burythehammer-claude-code-plugins to my agent?
Add the burythehammer/claude-code-plugins marketplace entry in Claude Code, enable the bundled provider skill, and invoke it from provider repos with Go and Terraform plugin framework tooling installed.
Comments
Share how you use burythehammer-claude-code-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.