菜单
Workflow for maintaining changelogs, READMEs, and documentation files. Use when adding changelog entries, updating docs after code changes, or synchronizing documentation with current behavior. Covers changelog categories, entry format, constraints, and validation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | doc-maintenance |
| description | Workflow for maintaining changelogs, READMEs, and documentation files. Use when adding changelog entries, updating docs after code changes, or synchronizing documentation with current behavior. Covers changelog categories, entry format, constraints, and validation. |
Active maintenance workflow for Envilder documentation: changelogs, READMEs,
and docs/ files.
Distinction from doc-sync: This skill covers how to write and update
documentation. The doc-sync skill covers how to detect drift across
documentation surfaces.
| Document type | Location |
|---|---|
| Changelogs (per-component) | docs/changelogs/{cli,gha,sdk-dotnet,sdk-python,sdk-nodejs}.md |
| Root README | README.md |
| CLI docs | docs/pull-command.md, docs/push-command.md |
| GHA docs | docs/github-action.md, github-action/README.md |
| SDK READMEs | src/sdks/{runtime}/README.md |
| Architecture docs | docs/architecture/ |
| Security docs | docs/SECURITY.md |
Use these categories matching existing style:
| Category | When to use |
|---|---|
Added | New features or capabilities |
Changed | Behavior changes to existing features |
Fixed | Bug fixes |
Documentation | Docs-only changes |
Dependencies | Dependency updates |
Security | Security-related changes |
## [1.2.0]: 2026-05-01
### Added
- Add `--profile` flag for AWS named profile support (#45)
### Fixed
- Fix Azure Key Vault timeout on large secret batches (#52)
doc-sync skill
for comprehensive audit)pnpm lint to check formatting and consistencyAfter documentation edits:
# Check formatting and consistency
pnpm lint
# For website-related docs, verify build
cd src/website && pnpm build
| Trigger | Delegate to | Why |
|---|---|---|
| Website pages need updating | website-design-system + website-i18n skills | UI patterns and i18n workflow |
| Unsure if documented behavior matches code | Verify against source directly | Read the actual implementation |
| Cross-surface drift suspected | doc-sync skill | Systematic drift detection |
| SDK docs need updating after version bump | sdk-release-checklist skill | Full integration checklist |
Workflow for investigating and reproducing bugs before fixing via TDD. Use when a bug report or GitHub issue is received. Covers issue fetching, root cause analysis, reproduction planning, and handoff to TDD cycle.
CRAP score quality gate for code complexity and test coverage. Use when reviewing methods for complexity risk, deciding whether to split methods, or determining minimum test coverage requirements.
Code smell detection and safe incremental refactoring patterns. Use when improving code structure, reducing technical debt, or cleaning up after a TDD cycle. Covers SOLID principles, smell catalog, and the propose-apply workflow.
Five independent analysis perspectives for code review: correctness, architecture, security, conventions, and complexity. Use when reviewing PRs, commits, or local changes. Includes severity model and output format.
Index of Architecture Decision Records (ADRs) for cross-cutting technical decisions. Use when making design choices, reviewing proposals for consistency with prior decisions, or onboarding to understand why specific tools or patterns were chosen. Covers test tooling, SDK architecture, code quality, and acceptance test infrastructure.
Git commit messages, PR workflow, and branching strategy using Conventional Commits and Semantic Versioning. Use when creating commits, pull requests, or managing Git workflow.