devops-skills

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.

Detect and analyze infrastructure drift between Terraform state and actual resources

Compare Terraform configurations across environments (dev, staging, prod)

Execute plan in batches with review checkpoints

Auto-generate documentation for Terraform modules and infrastructure

Run terraform plan with parallel agent analysis for comprehensive risk review

Comprehensive infrastructure-as-code review for Terraform configurations

Analyze Terraform provider or module upgrades for breaking changes and risks

Create detailed implementation plan with bite-sized tasks

Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Great work! Now let me use the code-reviewer agent to review the implementation against our plan and coding standards" <commentary>Since a major project step has been completed, use the code-reviewer agent to validate the work against the plan and identify any issues.</commentary></example> <example>Context: User has completed a significant feature implementation. user: "The API endpoints for the task management system are now complete - that covers step 2 from our architecture document" assistant: "Excellent! Let me have the code-reviewer agent examine this implementation to ensure it aligns with our plan and follows best practices" <commentary>A numbered step from the planning document has been completed, so the code-reviewer agent should review the work.</commentary></example>

Use when multiple agents disagree or provide conflicting recommendations. Analyzes different positions and either reconciles them or escalates to the user with clear options.

Use when categorizing and assessing infrastructure drift. Analyzes differences between Terraform state and actual infrastructure to identify causes and recommend resolutions.

Use when analyzing git history and past changes to identify patterns, similar incidents, and lessons learned. Dispatched as part of the parallel plan review workflow.

Use when reviewing Terraform plans for security implications, IAM changes, network rules, and compliance concerns. Dispatched as part of the parallel plan review workflow.

Use when analyzing terraform plan output for risks, impact assessment, and potential service disruptions. Dispatched as part of the parallel plan review workflow.

Use when generating documentation for Terraform modules, infrastructure, or runbooks. Creates READMEs, operational guides, and architecture docs.

Use before any Terraform or AWS operation to verify correct credentials and profile are active. Prevents cross-environment accidents.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when analyzing git history and past changes to identify patterns, recurring issues, and lessons learned from infrastructure changes.

Use when analyzing Terraform provider or module upgrades for breaking changes, deprecations, and migration requirements.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when detecting infrastructure drift between Terraform state and actual AWS resources. Identifies out-of-band changes.

Use when analyzing terraform/tofu plan output for risks, security issues, and potential service disruptions. Required before any apply operation.

Use when performing Terraform state surgery - state mv, import, rm operations. Requires extra safety measures.

Use when implementing any feature or bugfix, before writing implementation code

Use when starting any conversation - establishes mandatory skill invocation for both Development AND Operations workflows

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

3 hooks across 2 events