docs: Recommend dotagents QA for runtime changes#129
Merged
Conversation
Point agents to the existing Docker QA skill when changes affect CLI wiring, generated configuration, user scope, or package runtime behavior. Keep the guidance proportional rather than requiring the full playbook for every change. Co-Authored-By: OpenAI Codex <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Point coding agents to the repository's existing Docker QA skill when changes affect dotagents runtime behavior.
The repository instructions currently stop at
pnpm check, so agents can miss the higher-fidelity install, sync, generated-config, symlink, and user-scope checks already documented inskills/dotagents-qa/SKILL.md. This adds soft, proportionate guidance in the sharedAGENTS.mdrather than changing Garfield or requiring the full QA playbook for every change.