Overview
I scanned open issues for documentation-related wording and cross-referenced the current docs. I found a small set of real doc-quality signals, but several are already covered by existing pages and mainly need a clearer pointer.
Key findings
Already-documented behavior
Gap summary
- Clear docs gap: HTML comment sanitization / metadata guidance.
- Mostly answered already: GH_AW_GITHUB_TOKEN and self-hosted runner prerequisites.
- Doc-vs-behavior mismatch: .github/agents imports on non-Copilot engines.
Next actions
- Add an explicit note in safe-outputs docs about HTML comments being stripped.
- Consider a short self-hosted runner prerequisites checklist near the setup entry point.
- Verify whether the agent-import behavior still matches the current docs promise.
Generated by 💻 Dev · 10 AIC · ⌖ 3.16 AIC · ⊞ 9.1K · ◷
Add label dev to run again
Overview
I scanned open issues for documentation-related wording and cross-referenced the current docs. I found a small set of real doc-quality signals, but several are already covered by existing pages and mainly need a clearer pointer.
Key findings
Documentation missing for GH_AW_GITHUB_TOKEN magic secret #20593
Documentation missing for GH_AW_GITHUB_TOKEN magic secretSelf hosted runner pre-requisite on kubernetes are not clear #40107
Self hosted runner pre-requisite on kubernetes are not clearBug: .github/agents imports on Claude/Codex take fragile prompt-assembly path; .github/snippets avoids it #19611
Bug: .github/agents imports on Claude/Codex take fragile prompt-assembly path; .github/snippets avoids it.github/agents/imports and say non-Copilot engines inject the markdown body as a prompt.Safe-output sanitizer strips HTML comments — no structured metadata channel for downstream workflows #18992
Safe-output sanitizer strips HTML comments — no structured metadata channel for downstream workflowsAlready-documented behavior
Don't filter "<...>" in code paragraphs or inline code in markdown posted to issues, issue comments and PR descriptions #18829
Don't filter "<...>" in code paragraphs or inline code in markdown posted to issues, issue comments and PR descriptionsLink redaction needs to be less strict #17513
Link redaction needs to be less strictGap summary
Next actions