chore: run review-memory weekly and keep lone inbox notes one review - #103
Merged
Merged
Conversation
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.
The review-memory skill can now run on a weekly schedule without losing notes. Until now it emptied the whole inbox after every run, so a note only got one run to find a matching note before being promoted. That made its own "sat alone for two reviews" rule impossible. Now a note that doesn't match anything is kept with a
Seen: <date>line and dropped on its second review. That gives notes two weeks to pair up on a weekly schedule.The skill also stops without creating a branch or PR when there's nothing to review (an empty inbox and no section over its cap) or when an earlier memory PR is still open. Mechanism issues skip the file-issue interview, since the notes already are the spec.
AGENTS.mdand the inbox header now say weekly instead of monthly.With this merged, the weekly routine prompt shrinks to:
Not user-visible, so there's no changelog entry and no E2E evidence.
Out of scope
The
memory/<date>branch name may need aclaude/prefix if cloud routines can only push those branches. Worth checking on the first scheduled run.