Show captured Wrighty skill responses in the docs - #146
Merged
Merged
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.
The docs describe conversational operations but do not show what an agent response looks like. Add captured Codex exchanges to the README and skill reference, preserving Markdown tables, emphasis, and inline code inside blockquotes for both prompts and responses.
The README shows a compact board overview with worker availability. The reference adds exact-item queueing and an excerpt explaining unsupported GitHub batches. Examples are labelled as test-tracker captures, with separate tracker states and variable agent wording.
Validation: matched the quoted content against recorded responses, checked all 68 local links and anchors, and passed
git diff --check. No application code changed.