glean-docs-refresh

You can verify Glean documentation freshness by running a workflow that cross-references internal markdown knowledge files against Context7 developer platform docs, categorizing discrepancies into new, outdated, and current items within a dated update report.

To find outdated API endpoints in your knowledge base, cross-reference internal markdown sources against Context7 official Glean developer docs via mcp__context7__query-docs, producing a prioritized report of potentially outdated endpoints and schemas.

Context7 documentation diffing works with local markdown knowledge bases by reading internal markdown sources, extracting topics and schemas, querying Context7 through mcp__context7__query-docs, and generating a categorized update report identifying documentation gaps.

Automate a weekly documentation diff report by scheduling freshness checks that query Context7 for current Glean developer platform docs, cross-reference internal markdown sources, and write categorized discrepancy findings into a dated updates directory.

Run a documentation freshness check during scheduled weekly intervals, on-demand for immediate comparisons, or at session start when the last report is older than seven days to prevent internal Glean knowledge from drifting out of date.

When comparing internal Glean docs to Context7, discrepancies are categorized into New in Glean, Potentially Outdated, Confirmed Current, and Gaps to Investigate, with Critical and High priority items surfaced immediately in the dated report.