docs(qa): Improve dotagents QA playbook#112
Merged
Merged
Conversation
Move the dotagents QA skill from a fixed smoke-test recipe to a guided Docker sandbox playbook. Add a repo-local QA image so agents get a stable Node, pnpm, and system-tool baseline while still designing fixtures and assertions from the diff. Document the stale tsbuildinfo trap in container copies and require generated outputs to be inspected as evidence. Co-Authored-By: OpenAI Codex <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
gricha
approved these changes
Jun 12, 2026
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
2 participants
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.
The dotagents QA skill now guides agents through change-specific end-to-end QA inside a Docker sandbox instead of presenting a fixed smoke-test recipe. The playbook asks the agent to inspect the diff, identify the behavior under test, build an appropriate fixture, run the built CLI, and inspect generated outputs as evidence.
This also adds a repo-local QA Docker image with the expected Node, pnpm, and system tools. The container copy instructions exclude stale TypeScript build-info files alongside dist artifacts so project references rebuild cleanly in the sandbox.
Validated by building the QA image, running the Docker QA flow through pnpm install/build/check and fixture install/list/doctor/sync/user-scope checks, and running git diff --check.