terraform-drift-detection
Use when detecting infrastructure drift between Terraform state and actual AWS resources. Identifies out-of-band changes.
What this skill does
# Terraform Drift Detection ## Overview Detect and categorize drift between Terraform-managed state and actual infrastructure. Drift indicates out-of-band changes that can cause problems during the next apply. **Announce at start:** "I'm using the terraform-drift-detection skill to check for infrastructure drift." ## The Process ### Step 1: Verify Environment ```bash # Verify AWS credentials and account aws sts get-caller-identity # Confirm we're in the right directory/environment pwd ls -la *.tf 2>/dev/null | head -5 ``` ### Step 2: Refresh State ```bash # Initialize if needed terraform init # Refresh state to detect drift terraform plan -refresh-only -out=drift.out # Convert to JSON for analysis terraform show -json drift.out > drift.json ``` ### Step 3: Analyze Drift Parse drift.json and categorize changes: #### Drift Categories | Category | Severity | Examples | |----------|----------|----------| | **Security Drift** | CRITICAL | Security groups, IAM, encryption | | **Configuration Drift** | HIGH | Instance settings, networking | | **Tag Drift** | LOW | Tags modified outside Terraform | | **Metadata Drift** | INFO | AWS-managed fields that change | ### Step 4: Dispatch Analysis Agent ``` Task(drift-detector) → Categorize and assess drift impact ``` **Agent should:** - Categorize each drifted resource - Assess impact of accepting vs rejecting drift - Identify potential causes (manual changes, AWS updates, etc.) ### Step 5: Present Findings ```markdown ## Drift Detection Report ### Summary - Total drifted resources: X - Critical drift: Y - High drift: Z - Low/Info drift: W ### Critical Drift (Requires Immediate Attention) | Resource | Attribute | State Value | Actual Value | |----------|-----------|-------------|--------------| | ... | ... | ... | ... | ### Potential Causes - Manual console changes: [list if detected] - AWS service updates: [list if detected] - Unknown origin: [list if detected] ### Recommended Actions 1. [Action for each drifted resource] ``` ### Step 6: Resolution Options Present user with options: 1. **Accept Drift**: Run `terraform apply -refresh-only` to update state to match actual 2. **Reject Drift**: Run `terraform apply` to revert actual infrastructure to match code 3. **Investigate**: Manual review needed before deciding 4. **Hybrid**: Accept some drift, reject other drift **Never auto-resolve drift. Always get user approval.** ## Common Drift Sources ### Intentional (Usually Accept) - AWS auto-scaling adjustments - Managed service updates - Emergency manual fixes (document these!) ### Unintentional (Usually Reject) - Console click-ops mistakes - Unapproved manual changes - Conflicting automation ### Systemic (Fix Root Cause) - Multiple tools managing same resources - Missing Terraform coverage - CI/CD race conditions ## Integration with Memory Store detected drift patterns: - Which resources commonly drift - Common causes in this environment - Resolution preferences Query memory before analysis: - Has this resource drifted before? - What was the cause last time? - What resolution was chosen? ## Verification Checklist Before presenting: - [ ] Refresh completed successfully - [ ] All drift categorized by severity - [ ] Root causes identified where possible - [ ] Resolution options are clear - [ ] No sensitive values exposed in output
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.