Run documentation browser checks on demand through an agent skill - #84
Merged
Merged
Conversation
Documentation previewThe preview has been removed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation validation spent roughly six minutes installing browsers and running the full layout matrix on every change. Remove browser setup, layout execution, and screenshot uploads from the Docs workflow while retaining renderer tests, JavaScript checks, strict builds, and generated-content verification.
Add
.agents/skills/docs-visual-review/SKILL.mdfor on-demand visual work. It reuses the existing locked browser suite, explains focused versus full runs, and guides screenshot inspection and interaction checks. Update contributor instructions so browser checks are no longer required for routine documentation edits.Validation: skill validator and workflow YAML parsing passed; 11 renderer tests, 51 documentation tests (9 build-only cases skipped in the source run), and 6 JavaScript tests passed. The clean strict build and its artifact checks passed. The documented focused browser command passed all 20 index checks; the built site responds through the existing preview server.