Prioritize newer files in vault organizing skills#7
Merged
Conversation
Add a Recency Priority section to vault-lint, vault-compact, vault-concepts, vault-tracker, and vault-maintain. Each skill now works the active surface newest-first by the updated frontmatter date (mtime fallback) and concentrates scrutiny on the freshest material, on the assumption that long-untouched objects are already settled. Older files are never excluded: they remain valid link targets, merge destinations, and canonical homes, and still get a structural check. Mirrored to top-level skills/ via scripts/sync-skills.sh. Signed-off-by: Mark Phelps <209477+markphelps@users.noreply.github.com>
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.
What
Adds a
## Recency Prioritysection to the five vault skills that organize, compact, lint, and maintain the active surface:vault-lint,vault-compact,vault-concepts,vault-tracker, and thevault-maintainorchestrator.Each skill now works the active surface newest-first, ranked by each object's
updatedfrontmatter date (falling back to filesystem mtime when absent), and concentrates scrutiny on the freshest material — on the premise that long-untouched objects are already organized correctly.Why
Older files have typically already been organized, so re-auditing them with equal weight wastes effort. Steering attention toward recently-touched objects — where active thinking lives and where new mismatches, overlaps, and gaps appear — makes each pass land where it matters most.
Design choices
updatedfrontmatter, mtime fallback — aligns with the existing Portent model and vault-lint's stale-page check.Per-skill tailoring
Source edits live in
vault/skills/; the top-levelskills/copies are mirrored viascripts/sync-skills.sh(also run by the pre-commit hook). Plugin validator passes.