Recent code changes in the repository have introduced documentation drift. The following changes need corresponding documentation updates.
Changes Requiring Documentation Updates
1. New gh-aw-upgrade-check internal workflow is undocumented
Commit(s): 319d6a3 (PR #19)
What changed: A new gh-aw-upgrade-check workflow was added in .github/workflows/gh-aw-upgrade-check.md and .github/workflows/gh-aw-upgrade-check.lock.yml. This is an internal-only scheduled workflow (no shim in gh-agent-workflows/) that runs on weekdays to check for new gh-aw releases and file issues tagged [gh-aw-upgrade]. It imports scheduled-report/rwx.md, the same reusable prompt used by docs-drift.
Documentation impact: The workflow is not mentioned in any documentation file. It should be documented in gh-agent-workflows/DEVELOPING.md since that file covers the architecture, internal workflows, and the scheduled-report/rwx.md reusable prompt pattern. Specifically:
- The architecture tree in
gh-agent-workflows/DEVELOPING.md (line 7-27) should note that gh-aw-upgrade-check exists as an internal-only workflow in .github/workflows/ that also imports scheduled-report/rwx.md
- The "Reusable prompts" section (line 53-64) already uses
docs-drift.md as the example; it would be helpful to mention gh-aw-upgrade-check as a second consumer to illustrate the reuse pattern
- Consider documenting it in root
DEVELOPING.md alongside the repository structure table, or in a note about internal workflows that live directly in .github/workflows/
Note: This workflow is correctly omitted from the consumer-facing tables in README.md and gh-agent-workflows/README.md since it's not installable via gh aw add.
Suggested Actions
Generated by Docs Drift
Recent code changes in the repository have introduced documentation drift. The following changes need corresponding documentation updates.
Changes Requiring Documentation Updates
1. New
gh-aw-upgrade-checkinternal workflow is undocumentedCommit(s): 319d6a3 (PR #19)
What changed: A new
gh-aw-upgrade-checkworkflow was added in.github/workflows/gh-aw-upgrade-check.mdand.github/workflows/gh-aw-upgrade-check.lock.yml. This is an internal-only scheduled workflow (no shim ingh-agent-workflows/) that runs on weekdays to check for newgh-awreleases and file issues tagged[gh-aw-upgrade]. It importsscheduled-report/rwx.md, the same reusable prompt used bydocs-drift.Documentation impact: The workflow is not mentioned in any documentation file. It should be documented in
gh-agent-workflows/DEVELOPING.mdsince that file covers the architecture, internal workflows, and thescheduled-report/rwx.mdreusable prompt pattern. Specifically:gh-agent-workflows/DEVELOPING.md(line 7-27) should note thatgh-aw-upgrade-checkexists as an internal-only workflow in.github/workflows/that also importsscheduled-report/rwx.mddocs-drift.mdas the example; it would be helpful to mentiongh-aw-upgrade-checkas a second consumer to illustrate the reuse patternDEVELOPING.mdalongside the repository structure table, or in a note about internal workflows that live directly in.github/workflows/Note: This workflow is correctly omitted from the consumer-facing tables in
README.mdandgh-agent-workflows/README.mdsince it's not installable viagh aw add.Suggested Actions
gh-aw-upgrade-checktogh-agent-workflows/DEVELOPING.md— mention it as an internal workflow that uses thescheduled-report/rwx.mdreusable prompt, alongsidedocs-driftDEVELOPING.mdabout internal-only workflows that live directly in.github/workflows/(likegh-aw-upgrade-check,ci.yml,release.yml)