Skip to content

docs-scanner: raise the bar for issue quality#24623

Open
dvdksn wants to merge 1 commit intodocker:mainfrom
dvdksn:ci/improve-docs-scanner
Open

docs-scanner: raise the bar for issue quality#24623
dvdksn wants to merge 1 commit intodocker:mainfrom
dvdksn:ci/improve-docs-scanner

Conversation

@dvdksn
Copy link
Copy Markdown
Contributor

@dvdksn dvdksn commented Apr 3, 2026

Summary

The nightly docs-scanner was filing too many low-signal issues: single Vale-catchable words ("currently", "still", "yet"), feature-gate language misidentified as stale framing (#24617), and vague "verify X" tasks (#24618, #24619). This rewrites the scanner instruction to focus on substantive problems a reader would actually notice.

Changes to .github/agents/docs-scanner.yaml:

  • Adds a 4-question self-check gate before any issue is filed (can I quote it? would a reader be misled? is it already caught by Vale/htmltest? is it a product feature gate?)
  • Explicitly excludes: broken links, single time-relative words, "Limited Access"/"Contact sales" language, vague verification tasks
  • Removes the implicit quota — "file zero if nothing substantive" is a success
  • Elevates cross-document contradiction detection as the primary signal
  • Adds a "Why this matters" section to the issue template to force impact reasoning

Learnings

  • The word "freshness" in the agent description subtly nudges the agent toward hunting stale language. Renaming to "quality scanner" shifts focus to reader impact.
  • Self-check questions need to cover ALL automated tooling exclusions (broken links, not just time-relative words) — an incomplete list causes the agent to file what the more specific questions don't cover.

Generated by Claude Code

Rewrites the scanner instruction to focus on substantive documentation
problems rather than mechanical style violations. Key changes:

- Adds a 4-question self-check gate before any issue is filed
- Explicitly excludes broken links, single time-relative words, feature
  gates (Limited Access, Contact sales), and vague verification tasks
- Replaces "max 3 per run" with "file zero if nothing substantive found"
- Elevates cross-document contradiction detection as the primary focus
- Adds "Why this matters" section to issue template to force impact reasoning
- Adds --repo docker/docs to gh commands for correctness outside repo root

Based on analysis of all agent/generated issues to date: borderline
issues like docker#24266, docker#24245, docker#24310 were all single Vale-catchable words;
bad issues like docker#24617, docker#24618, docker#24619 were feature-gate misidentification
and vague verification tasks.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
@dvdksn dvdksn added the status/review Pull requests that are ready for review label Apr 3, 2026
@dvdksn dvdksn requested a review from a team April 3, 2026 08:13
@netlify
Copy link
Copy Markdown

netlify bot commented Apr 3, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 19499d0
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/69cf768e2d22780008487d91
😎 Deploy Preview https://deploy-preview-24623--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/review Pull requests that are ready for review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants