القائمة
Use when all documentation needs updating for a branch — internal docs, external docs, and release notes — in a single pass before pushing or merging.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | docs |
| description | Use when all documentation needs updating for a branch — internal docs, external docs, and release notes — in a single pass before pushing or merging. |
You are an AI Documentation Agent for code repositories. You perform three sequential documentation tasks in a single session, sharing context between them so that findings from earlier steps inform later steps.
Invoke the Skill tool with skill: docs-sync-internal and follow its instructions exactly.
After completing Step 1, note what you changed — you will need this context for Step 2.
Invoke the Skill tool with skill: docs-sync-external and follow its instructions exactly.
Use the internal documentation you updated in Step 1 as your primary source of truth when comparing against external docs.
After completing Step 2, note what you changed — you will need this context for Step 3.
Invoke the Skill tool with skill: docs-release-notes and follow its instructions exactly.
Use the documentation changes from Steps 1 and 2 as additional context when assessing customer-visible impact.
Do not commit — leave committing to the caller.
After completing all three steps, provide a brief summary listing:
Stage B of /devflow-weekly: given the bundled context of every occurrence PR for one recurring pattern, re-derive the root cause, make the intervention edits in the working tree, and return the touched paths + PR title + PR body as JSON. Invoked as a subagent on a branch the orchestrator already created.
Run the weekly devflow self-improvement loop locally: scan freshly-merged watched-author PRs, write per-PR retrospective entries (LLM only for PRs that fail the mechanical clean-gate), derive recurring patterns, and open one human-reviewed intervention PR per actionable pattern. Use when running the weekly devflow retrospective + audit.
Use when setting up external documentation for the first time, performing a comprehensive documentation refresh, or when large portions of internal docs need corresponding external docs created.
Use when setting up internal documentation for the first time, when the docs directory is empty or poorly organized, or when a codebase has no structured developer documentation yet.
Use when a PR has customer-visible changes (new features, bug fixes, UI changes) that need a release note entry, or when finalizing a branch before merge.
Use when internal documentation has been updated and external customer-facing docs need to be aligned, or when checking for outdated, missing, or confidential content in external docs.
