Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From majestic-devops
Verifies DevOps/infrastructure code like Terraform and Ansible YAML against best practices, security, simplicity, maintainability, and documentation. Scores readiness and generates reports.
npx claudepluginhub majesticlabs-dev/majestic-marketplace --plugin majestic-devopsHow this skill is triggered — by the user, by Claude, or both
Slash command
/majestic-devops:devops-verifierThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comprehensive infrastructure code verification framework. Apply this when verifying DevOps/infrastructure code changes.
Scores infrastructure simplicity in Terraform/OpenTofu and Ansible configurations by analyzing file counts, custom modules/roles, directory depth, and variables to detect overengineering.
Analyzes Terraform, CloudFormation, and Pulumi IaC for module structure, state management, drift prevention, and security posture. Use when reviewing configs, auditing modules, or PRs adding cloud resources.
Analyzes Terraform and similar IaC (OpenTofu, Pulumi) stacks for module structure, state backends, environments, providers, naming/tagging conventions, security patterns, CI/CD, and testing. Activates on *.tf files during discovery.
Share bugs, ideas, or general feedback.
Comprehensive infrastructure code verification framework. Apply this when verifying DevOps/infrastructure code changes.
| Dimension | Skill | Content |
|---|---|---|
| Platform patterns | devops-platform-patterns | DO, Hetzner, AWS, Cloudflare checklists |
| Security | infra-security-review | State, secrets, network, compute, storage |
| Simplicity | devops-simplicity-checker | File count, modules, complexity scoring |
| Maintainability | devops-maintainability-checker | Naming, formatting, DRY, versions |
devops-platform-patterns for platform-specific checksinfra-security-review for securitydevops-simplicity-checker for simplicitydevops-maintainability-checker for maintainability# Find infrastructure files
find . -name "*.tf" -o -name "*.yml" | grep -E "(infra|ansible|terraform|tofu)" | head -50
# Detect platforms
grep -rh "provider\s" *.tf 2>/dev/null | head -10
| Check | Required |
|---|---|
| README.md exists | Yes |
| Architecture diagram | For 3+ resources |
| Variable descriptions | All variables |
| Output descriptions | All outputs |
| Cost estimate | Yes |
| Dimension | 10 Points | 7 Points | 4 Points | 0 Points |
|---|---|---|---|---|
| Best Practices | Current patterns | Minor gaps | Outdated | Deprecated |
| Platform | All checks pass | 1-2 issues | Missing patterns | Wrong usage |
| Security | No issues | Low severity | Medium issues | Critical |
| Simplicity | ≤5 files, no modules | 6-10 files | 11-15 files | >15, deep nesting |
| Maintainability | Clean, documented | Minor issues | Multiple issues | Unmaintainable |
| Documentation | Complete | README only | Partial | None |
| Score | Verdict | Action |
|---|---|---|
| 50-60 | SHIP | Ready for production |
| 35-49 | REVIEW | Fix warnings first |
| 20-34 | BLOCK | Fix critical issues |
| 0-19 | REWRITE | Fundamental issues |
# DevOps Verification Report
**Platforms:** [detected]
**Date:** [YYYY-MM-DD]
## Summary
| Dimension | Score | Status |
|-----------|-------|--------|
| Best Practices | X/10 | PASS/FAIL |
| Platform | X/10 | PASS/FAIL |
| Security | X/10 | PASS/FAIL |
| Simplicity | X/10 | PASS/FAIL |
| Maintainability | X/10 | PASS/FAIL |
| Documentation | X/10 | PASS/FAIL |
**Overall:** X/60 - SHIP/REVIEW/BLOCK
## Critical Issues
[List with code fixes]
## Warnings
[List with recommendations]