docs: add agent package adoption skills - #26
Merged
Conversation
drewstone
added a commit
that referenced
this pull request
Jul 30, 2026
rtk 0.30.1's `git log` filter reproduces `git log --no-merges`: merge commits
are removed from the result set. When the caller names a merge commit, it
vanishes and the caller is silently handed a DIFFERENT commit. Measured:
git log --no-walk --oneline 928295e
real -> 928295e Merge pull request #26 from tangle-network/...
rtk -> (nothing)
git log -1 --format='%H %s' 928295e
real -> 928295edde6eb51c6faf16d904d6dc6601c52713 Merge pull request #26...
rtk -> 047e4d53f42c1ed3eb4f82a1f82dac3590fddae2 feat(us-tax): exam grown...
git log --oneline -8 origin/main
real -> 8 commits, 2 of them merges
rtk -> the 2 merges dropped, 2 older commits back-filled; the count
matches and the content does not
No revision needs to be named for the substitution to happen, and there is no
signal that it happened. An agent auditing history reads a rewritten one.
The rtk source is not on this machine (no rtk crate under $HOME, nothing in
cargo's registry or git checkouts, and the binary carries CI build paths), so
this is fixed at the hook: a token-saving filter may drop output DETAIL, it may
never change WHICH object git reports on. The hook now refuses to hand rtk
1. any history listing (log / whatchanged / shortlog), with or without an
explicit revision, and
2. any other git command naming an explicit revision (object name, ref,
HEAD~n, reflog selector, range), so a future filter regression in
show / diff / branch / stash cannot corrupt a git fact either.
Blocked commands are not rewritten at all; real git runs. git status, git diff,
git add, git commit, git push and the rest keep their compaction.
tests/rtk-rewrite.test.mjs states the property so it survives an upstream fix:
for every command naming an object, either the hook blocks it or rtk reports
the same object real git does. Verified to fail with the guard removed — rtk
returned "969c235 main work" for a merge commit named as 0e4aeba.
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.
Summary
Verification