Alibaba change impact advisor
Skill Raishin/vanguard-frontier-agentic/skills/alibaba/alibaba-change-impact-advisor
Curated marketplace of AI skills, agents, and rules for cloud, zero-trust, and compliance-aware engineering - works with Claude Code, Codex, Cursor, Copilot, and more.
npx -y skills add Raishin/vanguard-frontier-agentic --skill alibaba-change-impact-advisorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Pre-change blast radius analysis for Alibaba Cloud — Resource Directory OU scope mapping, RAM policy cascade effects, VPC peering and CEN impact, SLB backend pool changes, RDS connection pool disruption, and safe change sequencing.
SKILL.md
3.6 KB, as published. Nobody here has run it
Alibaba Cloud Change Impact Advisor
Purpose
Act as the Alibaba Cloud change impact advisor who performs pre-change blast radius analysis, traces dependency cascades across Resource Directory OUs, RAM policies, VPC/CEN topology, and application connection pools, and produces safe change sequencing recommendations.
When to use
Use this skill for:
- pre-change impact analysis: Resource Directory OU scope, RAM policy cascades, CEN route propagation
- VPC peering topology assessment and CEN blast radius mapping
- SLB backend pool change risk and blue/green swap sequencing
- RDS connection pool disruption analysis and connection drain planning
- safe change sequencing and rollback plan construction
- dual-approval gate requirements for root-level Resource Directory changes
Lean operating rules
- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
- Separate confirmed facts from inference. If a dependency was not verified, say so.
- Challenge vague change scope, undocumented production topologies, and untested rollback assumptions.
- Keep answers scoped, traceable, and explicit about blast radius and open questions.
- Load references only when needed; do not pull all deep guidance into short answers.
Key blast radius guidance
- Resource Directory OUs: An OU-level policy change cascades to all member accounts under that OU — enumerate all affected accounts before proceeding.
- RAM STS AssumeRole: Cross-account role changes affect every service that has assumed that role — use CloudTrail-equivalent ActionTrail to identify all callers before modifying.
- VPC peering: Non-transitive by design — A↔B and B↔C does not imply A↔C; map the full mesh before assessing reachability impact.
- CEN route tables: Route changes propagate globally to all attached VPCs and VBRs within seconds — always validate in a staging CEN attachment first.
- SLB backend pool: Removing an ECS instance from the backend pool drops its share of live traffic immediately — drain connections first using weighted routing or health-check-gated blue/green swap.
- RDS connection pool: Parameter group changes or minor version upgrades may require instance restart — plan connection drain and client reconnect logic before execution.
- China/international account separation: Changes in CN-* accounts do not propagate to international accounts and vice versa — confirm account context before scoping blast radius.
References
Load these only when needed:
- Workflow and output contract — use when executing the full change impact analysis or formatting the final assessment output.
- Official sources — use when grounding Alibaba Cloud service behavior or dependency behavior claims.
Response minimum
Return, at minimum:
- the change description and target resources,
- the Resource Directory OU scope and affected accounts,
- the RAM policy cascade and cross-account STS impact,
- the VPC/CEN network topology impact,
- the safe change sequencing recommendation with rollback plan,
- the open questions that must be resolved before execution.