Repository navigation
feat(visualize): draw a change as the process it changes, not the code diff - #48
Merged
Merged
Conversation
…e diff /visualize on a change tended to draw file trees and code diffs. The skill now picks the altitude before the form: a change is drawn as the before and after of the behavior, in the actor's words, with file:line anchors on each step. It drops to code structure only when the question is about the code. Adds a process-change form as the default for a change, renames the code diff form to "What changes in the code", and updates the description, the resolver row, the README, and the verify-responsive cross-reference.
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
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.
/visualize on a change tended to draw file trees and code diffs. The skill
now picks the altitude before the form: a change is drawn as the before and
after of the behavior, in the actor's words, with file:line anchors on each
step. It drops to code structure only when the question is about the code.
Adds a process-change form as the default for a change, renames the code
diff form to "What changes in the code", and updates the description, the
resolver row, the README, and the verify-responsive cross-reference.