Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…
Install Review Docs
$ npx skills add hashicorp/terraform-provider-aws --skill review-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashicorp/terraform-provider-aws review-docs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/review-docs .claude/skills/review-docs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "review-docs" agent skill from https://github.com/hashicorp/terraform-provider-aws/tree/main/.agents/skills/review-docs into .claude/skills/review-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-docs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hashicorp/terraform-provider-aws/tree/main/.agents/skills/review-docsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hashicorp/terraform-provider-aws --skill review-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashicorp/terraform-provider-aws review-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-aws.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/review-docs .agents/skills/review-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-docs" agent skill from https://github.com/hashicorp/terraform-provider-aws/tree/main/.agents/skills/review-docs into .agents/skills/review-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-docs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashicorp/terraform-provider-aws --skill review-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashicorp/terraform-provider-aws review-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-aws.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/review-docs .cursor/skills/review-docs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-docs" agent skill from https://github.com/hashicorp/terraform-provider-aws/tree/main/.agents/skills/review-docs into .cursor/skills/review-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-docs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hashicorp/terraform-provider-aws.git --path .agents/skills/review-docs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hashicorp/terraform-provider-aws --skill review-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashicorp/terraform-provider-aws review-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-aws.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/review-docs .gemini/skills/review-docs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-docs" agent skill from https://github.com/hashicorp/terraform-provider-aws/tree/main/.agents/skills/review-docs into .gemini/skills/review-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-docs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hashicorp/terraform-provider-aws review-docsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hashicorp/terraform-provider-aws --skill review-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-aws.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/review-docs .github/skills/review-docs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-docs" agent skill from https://github.com/hashicorp/terraform-provider-aws/tree/main/.agents/skills/review-docs into .github/skills/review-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-docs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashicorp/terraform-provider-aws --skill review-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashicorp/terraform-provider-aws review-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashicorp/terraform-provider-aws.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/review-docs .opencode/skills/review-docs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-docs" agent skill from https://github.com/hashicorp/terraform-provider-aws/tree/main/.agents/skills/review-docs into .opencode/skills/review-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-docs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review-docs- GitHub stars
- 11k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 493 words
- Files
- 2 (incl. references)
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MPL-2.0
At a glance
Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…
- Works in 6 steps: # Resource → ## Example Usage (with at least ###… → ## Argument Reference → …
- Reviewing documentation changes
- SKILL.md covers Should the PR include docs?, Description openings, Argument and attribute… and Section structure, plus 5 more sections
- Reaches registry.terraform.io
What it does
Review Docs is an agent skill from hashicorp/terraform-provider-aws, published by the product's own GitHub organization. Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code fences, and the Import + Identity Schema section. Use when reviewing documentation changes, or when a PR adds/changes a resource or data source and its docs should be checked.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/import-section.md`).
It sits in DevOps & Cloud, covering Infrastructure as code. It works with Terraform and Amazon Web Services. The repository describes itself as: The AWS Provider enables Terraform to manage AWS resources. The licence is MPL-2.0.
When your agent uses it
- Reviewing documentation changes
- A PR adds/changes a resource
- Data source and its docs should be checked
Example prompts
- “/review-docs”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- # Resource
- ## Example Usage (with at least ### Basic Usage)
- ## Argument Reference
- ## Attribute Reference
- ## Timeouts (only if the resource exposes timeouts)
- ## Import (only for resources)
What it can do on your machine
Read from SKILL.md and the folder at commit 972faab. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
registry.terraform.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Review Docs loads about 1.3k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 97 tokens; SKILL.md has 493 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from hashicorp/terraform-provider-aws at commit 972faab, republished under its MPL-2.0 licence (© hashicorp). 493 words, ~1,266 tokens.
Download SKILL.mdSave it as
.claude/skills/review-docs/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- review-docs
- description
- Review a Terraform AWS Provider PR's end-user documentation (website/docs/**/*.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code fences, and the Import + Identity Schema section. Use when reviewing documentation changes, or when a PR adds/changes a resource or data source and its docs should be checked.
<!-- Copyright IBM Corp. 2014, 2026 --><!-- SPDX-License-Identifier: MPL-2.0 -->Review: End-User Documentation
Assume the @maintainer persona. Scope: resource docs (r/), data source docs (d/), list resource docs (list/) under website/docs/, rendered at the Terraform Registry. Loaded from review-pr.
Authoritative reference: docs/end-user-documentation.md. When this skill and that document disagree, the document wins. Do not review CHANGELOG updates.
Should the PR include docs?
- If the PR adds or changes user-facing behavior (new resource/data source/attribute) but has no doc change, say what's missing.
- If the PR removes behavior but leaves stale docs, say what to remove.
- Review only the changed docs; don't review unchanged documentation except as needed for context.
Description openings
The single-line description: in frontmatter and the first paragraph after the H1 must use the verb for the doc type:
| Doc type | Opening verb |
|---|---|
| Resource | Manages … |
| Data source | Provides details about … |
| List resource | Lists … |
Flag openings like "This resource…", "Use this resource…", "Allows you to…", "Resource for…", or "Terraform resource for…".
Argument and attribute description style
Forbidden opening words: An, A, The, Defines, Indicates, Specifies. Rewrite "Indicates the amount of storage" → "Amount of storage." Always propose the corrected wording.
Don't spell out common abbreviations (e.g. "Amazon Resource Name (ARN)" → "ARN"). See Abbreviations for the full list and rationale.
Boolean arguments must start with Whether to:
- ✓
(Optional) Whether to enable logging. - ✗
(Optional) Enables logging./(Optional) If true, enables logging.
(Required) / (Optional) / (Read-Only) are the only valid markers, capitalized in parentheses, immediately after the hyphen.
Examples use example, not test. Flag any HCL block in docs that uses "test" as a resource label or name = "test".
Section structure
Resource docs, in this order:
# Resource: <aws_resource_name>## Example Usage(with at least### Basic Usage)## Argument Reference## Attribute Reference## Timeouts(only if the resource exposes timeouts)## Import(only for resources)
Data source and list resource docs have only Example Usage, Argument Reference, and Attribute Reference.
Show full SKILL.md (187 more words)Show less
Argument Reference
Required arguments come first, separated from optional by a header line. Alphabetize. Use these exact lead-ins:
The following arguments are required:
* `req_arg` - (Required) ...
The following arguments are optional:
* `opt_arg` - (Optional) ...If there are no required arguments, drop the "required" subsection — don't write "There are no required arguments."
For tagged resources, tags lives under optional arguments with this exact wording:
* `tags` - (Optional) Map of tags assigned to the resource. If configured with a provider [`default_tags` configuration block](/docs/providers/aws/index.html#default_tags-configuration-block) present, tags with matching keys will overwrite those defined at the provider-level.Attribute Reference
Open with This resource exports the following attributes in addition to the arguments above: (substitute "data source" / "list resource"). Flag pages that re-document arguments here — only computed attributes belong. Alphabetize.
For tagged resources, tags_all has this exact wording:
* `tags_all` - Map of tags assigned to the resource, including those inherited from the provider [`default_tags` configuration block](https://registry.terraform.io/providers/hashicorp/aws/latest/docs#default_tags-configuration-block).For tagged data sources, tags is a top-level computed attribute and there is no tags_all.
Code fences
Use terraform for .tf blocks and console for shell examples. Flag hcl (use terraform) or unfenced shell commands.
Style points
- Active voice, present tense. Don't document past or future behavior.
- Single-line description in frontmatter — flag multi-paragraph descriptions.
- Consistent terminology — match the AWS service's nouns; don't invent synonyms.
Import section & Identity Schema
The ## Import section (resources only) and its Identity Schema subsection have a precise required structure. See references/import-section.md for the full checklist and load it when the PR touches a resource's Import section.
© hashicorp, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .agents/skills/review-docs of hashicorp/terraform-provider-aws.
- SKILL.md
- references/import-section.md
Open the folder on GitHubat commit 972faab
Compare with similar skills
Review Docs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review Docs this skillhashicorp/terraform-provider-aws | 11k | — | ~1.3k | Automated safety check: Pass | MPL-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Terravision Cloud Diagramspatrickchugh/terravision | 1.6k | — | ~5.6k | Automated safety check: Notes | AGPL-3.0-only | |
| TerrasharkLukasNiessen/terrashark | 714 | — | ~843 | Automated safety check: Pass | MIT | |
| AWS Cloud Advisortech-leads-club/agent-skills | 7k | — | ~2.1k | Automated safety check: Pass | CC-BY-4.0 | |
| Spa Create Configsplunk/splunk-platform-automator | 137 | — | ~3.5k | Automated safety check: Pass | Proprietary |
Similar skills
Terravision Cloud Diagrams
patrickchugh/terravision
Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.
Terrashark
LukasNiessen/terrashark
Prevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps.
AWS Cloud Advisor
tech-leads-club/agent-skills
Answers AWS architecture, security and service-selection questions by searching AWS documentation through MCP tools first, then adapting advice to your stack and team.
Spa Create Config
splunk/splunk-platform-automator
A skill your agent uses when creating or updating splunkconfig.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for…
Provider Verification
mondoohq/mql
Verify mql provider resource/field changes against real cloud infrastructure.
More from hashicorp/terraform-provider-aws
All 17 skills in this repo- Official
Review Helpers
hashicorp/terraform-provider-aws
Review Terraform AWS Provider helper code: finders, status functions, waiters, sweepers, data sources, and list resources.
- Official
Review Identity
hashicorp/terraform-provider-aws
Review Terraform AWS Provider Resource Identity: the identity-strategy annotations (@ArnIdentity, @SingletonIdentity, @IdentityAttribute), multi-attribute @ImportIDHandler parsers, and region…
- Official
Review Lifecycle
hashicorp/terraform-provider-aws
Review Terraform AWS Provider resource lifecycle: CRUD step order, smerr/smarterr error handling, and AutoFlex model-to-SDK conversion.
- Official
Review Schema
hashicorp/terraform-provider-aws
Review Terraform AWS Provider Plugin Framework schema shape: model structs, Required/Optional/Computed combinations, plan modifiers (no ForceNew), nested-block custom types, validators, sensitive…
- Official
Review Tags
hashicorp/terraform-provider-aws
Review Terraform AWS Provider tagging: the tags/tagsall schema attributes, the @Tags(identifierAttribute=...) annotation, and wiring input.Tags = getTagsIn(ctx) after flex.Expand.
- Official
Review Tests
hashicorp/terraform-provider-aws
Review Terraform AWS Provider acceptance and unit test basics: required basic and disappears tests, TestAcc naming, TestCase essentials (PreCheck/ErrorCheck/ProtoV5ProviderFactories/CheckDestroy)…
Related
Works with
Categories
Questions about Review Docs
What does Review Docs do?
Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…. Review Docs is an agent skill from hashicorp/terraform-provider-aws, published by the product's own GitHub organization.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code fences, and the Import + Identity Schema section.
When should I use Review Docs?
Review Docs fits situations like: reviewing documentation changes; A PR adds/changes a resource; data source and its docs should be checked.
How do I install Review Docs in Claude Code?
Run `npx skills add hashicorp/terraform-provider-aws --skill review-docs -a claude-code`. Or copy the skill folder (.agents/skills/review-docs in hashicorp/terraform-provider-aws) into .claude/skills/review-docs in your project. Claude Code loads it when a task matches its description.
How do I install Review Docs in Codex?
Run `npx skills add hashicorp/terraform-provider-aws --skill review-docs -a codex`. Or copy the skill folder (.agents/skills/review-docs in hashicorp/terraform-provider-aws) into .agents/skills/review-docs in your project. Codex loads it when a task matches its description.
Can I use Review Docs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashicorp/terraform-provider-aws --skill review-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-docs, .gemini/skills/review-docs, .github/skills/review-docs and .opencode/skills/review-docs in your project.
What does Review Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Review Docs is instructions for the agent only.
Does Review Docs access the network?
SKILL.md names 1 domain. In commands or code: registry.terraform.io; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Review Docs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Review Docs use?
Review Docs is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Review Docs use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 467 tokens, read only when the agent opens those files.
What are the alternatives to Review Docs?
Skills that share tags, products or a category with Review Docs: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Terravision Cloud Diagrams (patrickchugh/terravision, 1.6k stars), Terrashark (LukasNiessen/terrashark, 714 stars) and AWS Cloud Advisor (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Docs?
hashicorp (a GitHub organization, an official publisher) maintains it in hashicorp/terraform-provider-aws, which has 11,109 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.
Source: hashicorp/terraform-provider-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.