aoa-safe-infra-change
Make bounded infrastructure, configuration, service, or operational changes with explicit risk framing, proportional verification, and rollback thinking. Use when a change has runtime or deployment implications and needs stronger discipline than a normal code edit. Do not use for purely local code changes, or when the main need is approval classification or preview-first execution.
- License 许可
- Apache-2.0
- 最近更新
- 2026-07-15
- Stars
- ★ 15
- Forks
- 1
01 前言 Front Matter
- name
- aoa-safe-infra-change
- license
- Apache-2.0
- metadata
- { "aoa_scope": "risk", "aoa_status": "canonical", "aoa_source_repo": "8Dionysus/aoa-skills", "aoa_invocation_mode": "explicit-only", "aoa_portable_profile": "codex-facing-wave-3", "aoa_source_skill_path": "skills/risk/aoa-safe-infra-change/SKILL.md", "aoa_technique_dependencies": "AOA-T-0028,AOA-T-0001" }
- description
- Make bounded infrastructure, configuration, service, or operational changes with explicit risk framing, proportional verification, and rollback thinking. Use when a change has runtime or deployment implications and needs stronger discipline than a normal code edit. Do not use for purely local code changes, or when the main need is approval classification or preview-first execution.
- compatibility
- Designed for Codex or similar coding agents with repository file access and an interactive shell. Network access is optional and only needed when repository validation or referenced workflows require it.
02 资源文件 11
- 参考文档agents/openai.yaml440 B
- 资产文件assets/infra_change_contract.template.json680 B
- 资产文件assets/infra_change_report.schema.json1.6 KB
- 资产文件assets/large-logo.svg442 B
- 资产文件assets/small-logo.svg440 B
- 参考文档checks/review.md1.0 KB
- 参考文档examples/runtime.md1.2 KB
- 参考文档references/risk_surface_matrix.md406 B
- 参考文档references/verification_and_rollback_ladder.md419 B
- 脚本scripts/infra_change_contract.py6.1 KB
- 脚本scripts/risk_surface_scan.py3.1 KB
03 SKILL.md 正文
aoa-safe-infra-change
Intent
Use this skill to shape infrastructure, service, configuration, or operational changes into a safer bounded workflow.
Trigger boundary
Use this skill when:
- the task changes infrastructure, services, configuration, orchestration, or operational surfaces
- the change has runtime, safety, or deployment implications
- the task needs stronger verification and rollback thinking than a normal code edit
Do not use this skill when:
- the task is a purely local code change with no operational implications
- a more specific risk skill should be used instead
- the operator has not provided enough authority for the requested action
- the main question is whether authority exists at all; use
aoa-approval-gate-check - the main need is to prefer or interpret a preview path before execution; use
aoa-dry-run-first
Inputs
- target change
- touched operational surfaces
- stated authority or approval state
- validation path
- rollback idea
Outputs
- explicit risk-aware plan
- bounded infrastructure or config change, or bounded execution recommendation
- verification result
- report with remaining risk notes
Procedure
- identify the operational surface and main risk
- confirm whether the change belongs to a high-risk or explicit-only category
- keep the change small and reviewable
- avoid unrelated cleanup or hidden expansion of scope
- verify the result using the strongest practical bounded checks available
- report what changed, what was verified, and what remains risky or deferred
Contracts
- infrastructure changes should stay explicit and reviewable
- risk should be named before apply, not after failure
- verification should be stronger than symbolic confidence
- rollback thinking should exist before execution
Risks and anti-patterns
- treating infra edits like ordinary code edits
- making broad config or orchestration changes under a narrow task label
- relying on weak verification for changes with real runtime impact
- skipping explicit risk framing because the diff looks small
Verification
- confirm the operational surface was named clearly
- confirm the change stayed bounded
- confirm verification was explicit and proportional to the risk
- confirm rollback or recovery thinking was present before execution or recommendation
- confirm the report includes unresolved risk or recovery notes
Technique traceability
Manifest-backed techniques:
- AOA-T-0028 from
8Dionysus/aoa-techniquesatcd276f040d55d490bd015b8698c7a5d594b9f875using pathtechniques/execution/agent-workflows-core/confirmation-gated-mutating-action/TECHNIQUE.mdand sections: Intent, When to use, Inputs, Outputs, Core procedure, Contracts, Risks, Validation - AOA-T-0001 from
8Dionysus/aoa-techniquesatcd276f040d55d490bd015b8698c7a5d594b9f875using pathtechniques/execution/agent-workflows-core/plan-diff-apply-verify-report/TECHNIQUE.mdand sections: Intent, Outputs, Contracts, Risks, Validation
Adaptation points
Future project overlays may add:
- local risk classifications
- approval rules
- preferred validation commands
- rollback or recovery expectations
04 同仓库更多 Skills
deploy-app
Deploy the application to staging or production environments.
deploy
Deploy the application to environments.
building-native-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
create-section
Use when creating a new section for the AI Workshop presentation. Guides through title slide setup, layout choices, and content gathering. Activates when user wants to add a new topic section to the slideshow.
ship-checker
Run a full pre-ship review for this repo. Use when asked if a change is ready to deploy, publish, or ship.
lint-check
Run repository linters and report failures.