Repository navigation
fix(registry): skip test fixture SKILL.md files - #304
Merged
Merged
Conversation
A Repository that ships one Skill beside test fixtures was counted as a multi-Skill Repository, so its Skill lost the repository URL. One shared path predicate now decides what counts as a Skill at every discovery path, and a migration clears the tree cursor on affected Repositories so the next sync retires the fixture rows.
1 task done
harlan-zw
added a commit
that referenced
this pull request
Sep 29, 2026
The migration naming check rejects a gap, and 0124 is not on main yet. #304 also claims 0124, so whichever pull request merges second renumbers.
This was referenced Sep 29, 2026
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.
❓ Type of change
📚 Description
harlan-zw/nuxt-ai-readyships one Skill plus two fixtures undertest/fixtures/agent-skills/skills/. The indexer counted all three, so the real Skill lives at/gh/harlan-zw/nuxt-ai-ready/nuxt-ai-readyinstead of/gh/harlan-zw/nuxt-ai-ready. Any maintainer who tests a package Skill hits the same thing.Every discovery path now asks one predicate. A
SKILL.mdis ignored when a parent folder istest,tests,__tests__,fixture,fixtures,__fixtures__,e2e,testdataornode_modules. The Skill's own folder never counts, so.claude/skills/test/SKILL.md(facebook/react) stays.Production today, resolved rows only:
testsfixturestest__tests__fixturee2etestdata,__fixtures__,node_modulesThat is 180 rows across 36 Repositories after overlap. None has a like. Five are indexable, and all five are fixtures:
boshu2/agentopsknown-good and known-bad,garrytan/gstackalpha and beta, and onepbakaus/impeccableoracle workspace.I left
examples,samplesandtestingin. They hold 139 resolved rows, 48 indexable, and a lot of them are real Skills:muratcankoylan/agent-skills-for-context-engineering/examples/*,skills/testing/*in several Skill packs. Some are demo noise (langchain-ai/deepagents/examples,sylphai-inc/atskills), so a later pass could handle those per Repository.📝 Migration
Existing fixture rows go through the sweep sync already uses for a deleted Skill:
path_missing, quarantined, noindex. An unchanged tree SHA skips that sweep, so0124_resync_fixture_skill_repos.sqlclearslast_tree_shaon the 36 affected Repositories. The deploy applies it, and the hourly sync reaches each Repository on its normal rotation. The SQL only chooses which Repositories to resync; the TypeScript predicate still decides which rows go.Open question: a Repository whose only SKILL.md files are fixtures now syncs as
no_supported_skill_pathsand getsbroken_since. That looks right to me, but it drops out of the general rotation.