Repository navigation
feat(registry): follow renamed Skills with an alias redirect - #640
Merged
Merged
Conversation
The scheduled sync declines to admit new Skills in a submitted Repository, then records the tree it saw. Later syncs and index requests skip that tree as unchanged, so renamed or added Skills never enter. An index request for a stale indexed Repository now queues a submission, and a submission rereads an unchanged tree.
A renamed Skill folder read as a removal and an addition: the old page became a 410, its likes and collection entries stayed behind, and old run commands failed. Sync now pairs a missing Skill with a new one whose SKILL.md body matches, moves its rows, and keeps the old name as an alias that answers with a 301 (ADR-0017).
harlan-zw
added
the
harlan-agent-review
harlan-github-agent
Bot
added
harlan-agent-review-required
Contributor
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. The pull request is not ready for review. |
harlan-github-agent
Bot
removed
the
harlan-agent-running
1 of 6 tasks
harlan-github-agent
Bot
removed
the
harlan-agent-review-required
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.
❓ Type of change
📚 Description
Follows #638.
When an author renamed a Skill folder, the registry saw a removal and an addition. The old page became a 410, its likes and collection entries stayed behind,
skilld runwith the old name failed, and the new name started with no history. On 2026-10-13 harlan-zw/brundlefly renamedim-not-a-flyandim-a-flythis way.A sync's final sweep now pairs a missing Skill with a Skill first seen in the same sync. Their
SKILL.mdbodies must share at least 60% of their lines, and each must be the other's single best match. Brundlefly's renamed Skills scored 0.97 and 0.99 against their old copies and 0.00 against everything else. The old name's rows move through the same table list as a Repository move, and the old name stays in a newskill_aliasestable. Old Skill URLs answer one 301, andskilld runwith the old name resolves to the new identity. A removal without a match keeps its 410. ADR-0017 records the decision and its limits.