Add end-to-end-doctesting skill#367
Open
JoshKappler wants to merge 2 commits into
Open
Conversation
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.
Adds an agent skill that smoketests the setup docs by being the user: point it at a docs branch or PR and it sets up GT from scratch in a throwaway project, following the docs exactly as written, and reports where they break. Most first-time users now point an agent at the docs and say "install this" — an agent following the docs verbatim is the representative first-run experience, so where it gets stuck, users get stuck.
Usage:
A single flow runs 10–30 min; with no scope it sweeps every actionable instruction in the tree. Output is a short glanceable verdict plus a findings report where each finding carries a concrete suggested edit against the exact file and line. It never posts review comments or pushes anything on its own — that only happens on an explicit "file it".
Trial runs against the docs-refactor branch (gt-cloud#3427) surfaced 7 real issues in the Next quickstart alone — e.g. the root-layout snippet silently drops globals.css/fonts/metadata, and the finished app ships no
<html lang>.Layout: the skill lives in
.agents/skills/next todocs-skill;.claude/skills/end-to-end-doctestingis a symlink so Claude Code picks it up, andagents/openai.yamlcarries the metadata for OpenAI-style agents.