القائمة
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use for UI, frontend, styling, landing page, or component creation; injects palettes, typography, layouts, motion, and anti-generic design rules.
Use for frontend, backend, mobile, debugging, security, or specialized engineering work that needs focused domain references and strict boundaries.
Use when an approved plan has independent tasks ready for delegated execution with fresh subagents and two-stage review.
Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
Use when committing or pushing completed work; automates gate-aware conventional commits with optional signing and CI/CD checks.
| name | codex-docs-change-sync |
| description | Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation. |
| load_priority | lazy |
Map code changes to affected documentation via map_changes_to_docs.py. Report-only by default, no auto-edit. Scope: auto-detect staged -> unstaged -> last commit. Fallback: manual diff inspection.
Identify documentation that is likely affected by code changes.
docs steps.$codex-docs-change-sync.map_changes_to_docs.py for report-only docs impact mapping.skills/.system/REGISTRY.md for full script paths.--help before invoking map_changes_to_docs.py.If scope is not specified, use auto mode:
Report which scope was selected.
If script cannot run, inspect diffs manually and report likely docs using the
conventions in references/mapping-rules.md (path→doc mapping, reference-search
patterns, always-include rules): start from docs/, README.md, CHANGELOG.md,
and module-specific docs.
references/docs-sync-spec.md: script behavior, output format, and fallback protocol.references/mapping-rules.md: default code→docs mapping conventions, reference-search patterns, always-include rules, and confidence levels (the human-readable spec behind the script and the manual fallback).