fix(productivity): prevent date-label drift and name-variant duplicates in update skill#263
Open
hp-8 wants to merge 1 commit into
Open
fix(productivity): prevent date-label drift and name-variant duplicates in update skill#263hp-8 wants to merge 1 commit into
hp-8 wants to merge 1 commit into
Conversation
…es in update skill Add date discipline rules requiring ISO date anchoring before any day-of-week label, and fuzzy-match guard against existing memory before flagging entities as new suggestions. Fixes anthropics#216
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
Two markdown-only inserts to
productivity/skills/update/SKILL.mdthat fix recurring drift modes in/productivity:update:YYYY-MM-DD (DayOfWeek)) before any day-of-week label, preventing the model from carrying forward stale day labels across scheduled runsmemory/people/andmemory/projects/by full name, email handle, last name, and acronym before flagging an entity as new — catches nickname/full-form collisions (e.g. "Sue" vs "Susan")Fixes #216