Run any Skill in Manus with one click

pulumi-modify-existing

Stars2

Forks0

UpdatedMarch 20, 2026 at 21:29

Modify existing Pulumi infrastructure stacks safely. Use this skill when making any Pulumi IaC changes — always edit the existing stack entrypoint, never create new files, preserve assumeRole and cross-account configuration, and validate with pulumi preview before finishing.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

mitodl

mitodl/agent-kit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	pulumi-modify-existing
description	Modify existing Pulumi infrastructure stacks safely. Use this skill when making any Pulumi IaC changes — always edit the existing stack entrypoint, never create new files, preserve assumeRole and cross-account configuration, and validate with pulumi preview before finishing.
license	BSD-3-Clause
metadata	{"category":"infrastructure"}

Pulumi: Modify Existing Files

Always modify, never create

Infrastructure changes belong in the existing entrypoint for the stack (typically __main__.py). Do not create additional Pulumi files unless the stack already follows a multi-file pattern that makes a new file the right fit.

Preserve existing functionality

When editing a Pulumi stack entrypoint, the following must never be silently removed:

assumeRole / cross-account role configuration — removing this breaks production deployments that depend on cross-account access.
Existing resource exports (pulumi.export(...)).
Stack references to other stacks.

Before finalizing changes, scan the diff to confirm nothing was deleted unintentionally.

Validate changes before declaring done

After modifying any Pulumi code, run a preview to confirm the plan is correct:

pulumi preview --stack <stack-name>

Review the output carefully:

Unexpected resource replacements or deletions are bugs, not acceptable side effects.
"0 changes" is only correct if you genuinely expected no changes.

More from this repository

same repository

address-pr-feedback

mitodl/agent-kit

Fetch, categorize, and address GitHub pull request review feedback -- inline review comments, review threads, top-level discussion comments, and failing status checks (GitHub Actions jobs plus third-party checks like pre-commit.ci, GitGuardian, and CodeQL) -- including paginating through large or long-running PRs with many rounds of review. Applies fixes, replies to reviewers with evidence (never a generic "noted"), marks resolved review threads via the GraphQL API, and diagnoses/fixes failing checks using their logs. Use this skill when asked to "address PR feedback", "address the comments on <PR>", "resolve the review comments", "mark addressed comments as resolved", "fix the failing checks", "the CI is red on <PR>", or to triage feedback from bots (Copilot, Gemini, CodeQL, Sentry), third-party check services (pre-commit.ci, GitGuardian), or human reviewers on a specific pull request.

2026-07-132

witan-code

mitodl/agent-kit

Tree-sitter code graph for symbol lookups, caller graphs, change-impact analysis, and cross-repo contract tracing. Use instead of grep/Explore when you need exact symbol definitions, who-calls-what, blast radius before an edit, or which repo provides/consumes a shared env var, endpoint, package, or service. `/witan-code` reports whether the current repo is indexed and lists the available `code_*` tools; `/witan-code reindex` forces a full rebuild. Backed by the witan-code MCP server (code_* tools).

2026-07-092

github-pr-triage

mitodl/agent-kit

Enumerate your open GitHub pull requests across an org (or a single repo) and categorize each by the action it actually needs: needs a first-pass bot review (Copilot/Claude/Gemini), awaiting a requested reviewer, has review feedback to address, formally has changes requested, or is approved and ready to merge. Use this skill when asked for a PR status report, to triage an open-PR backlog, to find PRs ready to merge, to see which PRs are stuck waiting on the author, or to process pull requests across a GitHub organization such as mitodl.

2026-07-092

witan-project-tracker

mitodl/agent-kit

Track an end-to-end engineering project across multiple agent sessions without explicit handoffs. Use this skill when starting a multi-session project (call workflow_project_create then workflow_session_start), when continuing an existing project in a new session (call workflow_session_start with the slug injected by the context hook/extension), when advancing phases (workflow_project_advance), when closing a session (workflow_session_end), or when completing a project (workflow_project_complete to create a corpus trace). Requires the witan MCP server. Covers project lifecycle, cross-session linking, parallel sessions, phase transitions, and corpus trace creation for pattern mining.

2026-07-082

witan-workflow

mitodl/agent-kit

Interactive workflow session manager. Call at the start of any session to link it to a tracked project. Lists active WorkflowProjects for the current repo, lets the user pick one (or create a new project), then calls workflow_session_start to register the session in the graph. Also supports ending a session (/witan-workflow end) or listing all projects (/witan-workflow list). Requires the witan MCP server.

2026-07-082

witan-memory

mitodl/agent-kit

Read from and write to the team's shared agent memory graph. Prefer this over your private built-in/session memory for any durable, team-shareable knowledge. Use when starting work in a repository (load project facts and patterns), after solving a non-obvious problem (store a pattern), when discovering structural information about a codebase (store a project fact), when a correction was needed (store a lesson), or whenever you would otherwise save an engineering fact/lesson/decision to local session memory. Requires the witan MCP server to be configured.

2026-07-082

name	pulumi-modify-existing
description	Modify existing Pulumi infrastructure stacks safely. Use this skill when making any Pulumi IaC changes — always edit the existing stack entrypoint, never create new files, preserve assumeRole and cross-account configuration, and validate with pulumi preview before finishing.
license	BSD-3-Clause
metadata	{"category":"infrastructure"}

Pulumi: Modify Existing Files

Always modify, never create

Preserve existing functionality

When editing a Pulumi stack entrypoint, the following must never be silently removed:

assumeRole / cross-account role configuration — removing this breaks production deployments that depend on cross-account access.
Existing resource exports (pulumi.export(...)).
Stack references to other stacks.

Before finalizing changes, scan the diff to confirm nothing was deleted unintentionally.

Validate changes before declaring done

After modifying any Pulumi code, run a preview to confirm the plan is correct:

pulumi preview --stack <stack-name>

Review the output carefully:

Unexpected resource replacements or deletions are bugs, not acceptable side effects.
"0 changes" is only correct if you genuinely expected no changes.