Repository navigation
docs: correct -c framing for atomic diff, document --json - #3
Open
graywolf336 wants to merge 1 commit into
Open
graywolf336 wants to merge 1 commit into
graywolf336 wants to merge 1 commit into
Conversation
`atomic diff -c` was described as "compare against a specific change", which reads as a comparison target. It is a selector: the command answers two different questions depending on whether it is present — working copy vs. recorded state, or the state before vs. after a change. Agents were following the misleading phrasing. Also document --json (added in atomic#218), which takes precedence over the text format selectors, and note that a clean working copy now surfaces copy-pasteable -c commands rather than dead-ending. Append a trailing newline to code-intelligence/SKILL.md so the mirror stays byte-identical to the materialized working copy; the missing newline was the only diff between the two.
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.
Follow-up to atomic#218.
Changes
atomic-vcs/SKILL.md—atomic diff -cwas described as "compare against a specific change", which reads as a comparison target. It's a selector: the command answers two different questions depending on whether it's present (working copy vs. recorded, or before vs. after a change). This phrasing is what misled on stage.--json— added in #218, takes precedence over--stat/--name-only/--name-status; a-cdiff carries the change header underchange, a working-copy diff carriesview.-ccommands instead of dead-ending.code-intelligence/SKILL.mdso the mirror stays byte-identical to the materialized working copy.