pulumi-best-practices

Review Pulumi code for unsafe resource management and deployment patterns.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/Kristopherlb/shinobi-wan --skill pulumi-best-practices-kristopherlb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pulumi-best-practices
Source: https://github.com/Kristopherlb/shinobi-wan/tree/main/.agents/skills/pulumi-best-practices
Command: npx skills add https://github.com/Kristopherlb/shinobi-wan --skill pulumi-best-practices-kristopherlb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent common Pulumi infrastructure mistakes that cause deployment failures, broken dependencies, accidental resource replacement, and insecure configuration practices.

Core Features & Use Cases

  • Resource Management Guidance: Ensures correct Output handling, dependency tracking, component organization, and safe infrastructure refactoring patterns.
  • Deployment Safety Practices: Covers preview workflows, alias usage, secret management, and validation checks for reliable Pulumi deployments.
  • Use Case: Use this Skill when reviewing or writing Pulumi code for AWS infrastructure to identify risky patterns and improve maintainability before deployment.

Quick Start

Use the pulumi-best-practices skill to review my Pulumi code for deployment risks and recommended improvements.

Frequently Asked Questions about pulumi-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent accidental resource replacement when refactoring Pulumi infrastructure code?

To prevent accidental resource replacement during Pulumi refactoring, apply alias-based refactoring patterns and preview-driven deployment practices. This ensures Pulumi correctly tracks existing resources instead of deleting and recreating them.

What is the correct way to handle Pulumi Outputs for safe resource dependency tracking?

Correct Pulumi Output handling requires passing Outputs directly between resources rather than unwrapping them prematurely. This maintains proper dependency tracking and prevents deployment failures caused by missing infrastructure dependencies.

How do I securely manage secrets and configuration in AWS Pulumi deployments?

Securely managing Pulumi secrets requires applying proper secret protection and secure configuration management practices. This prevents exposing sensitive infrastructure data during AWS deployment workflows and resource provisioning.

What's the best way to organize component resources in Pulumi for better maintainability?

Organizing Pulumi component resources involves grouping related infrastructure logically to ensure correct Output handling and dependency tracking. This improves maintainability and simplifies infrastructure reviews before deployment.

Why does my Pulumi deployment fail due to unsafe resource management patterns?

Pulumi deployment failures often occur due to unsafe resource management patterns like broken dependencies or incorrect Output handling. Identifying and correcting these risky patterns ensures reliable infrastructure deployment.

Can I use this approach to review existing Pulumi code for AWS infrastructure risks?

Yes, you can review existing Pulumi code for AWS infrastructure to identify risky deployment patterns and insecure configuration practices. This process helps improve maintainability and deployment safety before applying changes.