Repository navigation
✨ Add local TDD screenshot commands - #368
Merged
Merged
Conversation
Let agents and humans inspect captures after a run without starting the TDD server. Keep baseline acceptance local and update the report so the selected comparison reflects the new baseline.
Point agents at captured images after a TDD run exits. Keep current-image iteration lightweight and make local baseline acceptance explicitly authorized.
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.
Why
A local TDD run already writes screenshots under
.vizzly, but reviewing them has depended on the report/server flow. Agents and people should be able to keep iterating after the run exits, open the current capture directly, and choose when they want to inspect a diff.Approach
Add
tdd screenshots list,latest,show, andaccept. These commands read local report data, print usable image paths, and let a selected current capture become its local baseline. The shipped Vizzly skill now guides agents to inspect current images first, use diffs when they help, and accept baselines only when authorized.Evidence
Dogfood exercised local capture review and baseline acceptance across the Vitest, Storybook, Ember, static-site, Ruby, and Swift examples. Focused CLI coverage and the production build pass. The Ruby example still has a repeatable 5.4% homepage difference with an unresolved cause; SwiftUI preview-specific dogfood could not run because the installed Xcode 27 does not match the runner's Xcode 26.6 requirement.