Fix cached-results path in literature-report skill#59
Merged
Conversation
rodneykinney
approved these changes
May 12, 2026
Member
rodneykinney
left a comment
rodneykinney
left a comment
There was a problem hiding this comment.
Thanks for catching this!
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
2 participants
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.
literature-reportpointed at.asta/literature/find/for cached search results, butfind-literatureactually writes them to.asta/documents/literature/find/(and indexes them viaasta documents add). The mismatch meantliterature-reportsilently missed the cache on every lookup and would have hit a permission prompt if it ever guessed the real path — itsReadallow-list was scoped to.asta/literature/*.Points both the docstring and the
allowed-toolsRead scope at the pathfind-literatureactually uses.