documentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
소스 정보
- 저장소
- Azure/agent-landing-zone
- 최근 소스 활동
- 2026년 10월 2일 23:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1,186
- 포크
- 322
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- documentation-consistency
- description
- Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
# AI Landing Zone documentation consistency
1. Identify the user, consumer, contributor, or operator behavior that changed.
2. Search `README.md`, `CHANGELOG.md`, `docs/`, `pipelines/README.md`, examples,
and tests for the parameter, output, flag, topology, command, and old term.
3. Update every affected in-repository source in the same change.
4. When the public Bicep landing-zone narrative changes, update the MkDocs source
on `Azure/AI-Landing-Zones` `main` and link the companion pull request.
5. Keep examples aligned with current defaults and both standard and network-
isolated modes.
6. Classify semantic-version impact and record migration guidance for breaking
behavior.
7. Report documentation status and any coordinated pull request in the handoff.
Generated `gh-pages` content is not an editable documentation source. A user-
visible change is incomplete until documentation is updated or a search proves
that no published page is affected.
GitHub에서 보기