Update, create, review, and find gaps in contributor documentation including CONTRIBUTING.md, docs/contributing/, and docs/architecture/. Use when a task affects contributor setup, build, test, debug, review, or architecture guidance, or when a code review needs a documentation impact assessment.
Use this skill to maintain contributor-facing documentation that must stay aligned with the Radius repository.
This skill applies to:
CONTRIBUTING.mddocs/contributing/docs/architecture/.github/ when the requested change is specifically about contributor workflowsDo not use this skill for general product documentation, end-user documentation, or code changes that have no contributor workflow impact.
The documentation structure under docs/contributing/ may change over time. Do not assume any specific sub-paths exist. Instead, discover the current layout at the start of every task:
docs/contributing/ to learn the current structure.CONTRIBUTING.md and any top-level index files (e.g., README.md files, table-of-contents pages) to understand the navigation hierarchy.docs/architecture/ contents when the task involves architecture documentation.Always verify the actual directory structure before referencing, creating, or moving any doc.
Follow this flow. After classifying the request, jump to the matching section under Modes for specific steps.
CONTRIBUTING.md and any relevant index or README files.Use this mode when the target page exists but is outdated, unclear, or incomplete.
Expected output:
Use this mode when the repository supports a contributor workflow that is not documented anywhere appropriate.
Expected output:
Use this mode when the user wants to know what contributor docs are missing or stale.
Inventory the existing contributor docs and summarize what each section already covers.
Scan the repository for contributor-relevant workflows, especially:
Cross-reference documented workflows against actual repository capabilities.
Report gaps in this format:
| Gap | Suggested Doc | Location | Priority |
|---|---|---|---|
| Description of what's missing | Proposed title | Proposed path | High/Medium/Low |
Prioritize using this rubric:
Expected output:
Use this mode when contributor docs changed and the request is for review, not direct editing.
Review focus:
Use this mode during code review when the changed code might require contributor doc updates.
Discover the current doc structure by following the Documentation Map procedure.
Categorize the change by contributor impact area:
| Change Type | Likely Doc Impact Area |
|---|---|
| New CLI command or flag | CLI guides, first-commit walkthroughs |
| Build system changes (Makefile, scripts) | Build and local dev guides |
| New package or directory | Repo organization guides |
| Test framework changes | Test execution guides |
| Config file changes | Control plane or runtime config guides |
| New prerequisites or tools | Prerequisites and setup guides |
| API schema changes | Schema and API change guides |
| Debugging workflow changes | Debugging guides |
| New dev workflow or script | Contribution pathway index or new guide |
| Architecture changes | docs/architecture/ |
| CI/CD workflow changes | Consider new guide |
| TypeSpec/API spec changes | Schema guides, docs/architecture/ |
| Helm chart or deployment changes | Consider deployment guide |
| Dev container changes | Prerequisites and setup guides |
| Code generation changes | Code writing or generation guides |
| Recipe changes | Consider recipe contribution guide |
| Copilot instruction/skill changes | .github/copilot-instructions.md |
Locate the specific doc that covers the impacted area by searching the discovered structure.
Assess whether contributor behavior changes. An update is usually needed if the change:
If an update is needed, specify:
If no update is needed, state why not.
Expected output:
Ask a clarifying question only when one of these is ambiguous:
Otherwise, proceed without asking.
/contributing-docs-updater Review the changes in the contributor test docs for accuracy./contributing-docs-updater Create a contributor guide for the local debug-start workflow./contributing-docs-updater Do these Makefile changes require contributor doc updates?/contributing-docs-updater Find gaps in the contributor docs for TypeSpec and Swagger workflows.Before finalizing any doc creation or update:
When operating in review-only modes, replace edits with precise findings and recommended doc changes.