feat: add OCX registry support#66
Merged
Merged
Conversation
- Create registry.jsonc with 48 components (11 skills, 24 agents, 9 commands, 3 bundles, 1 plugin) - Add standalone profile (Systematic only) at registry/files/profiles/standalone/ - Add OMO profile (Systematic + Oh My OpenCode) at registry/files/profiles/omo/ - Configure docs site to serve registry via .well-known/ocx.json discovery file - Symlink registry/files/ to existing bundled assets (skills/, agents/, commands/) All components follow OCX Registry Protocol v1 with proper namespacing and install targets.
Task 3: Registry build/validation script - Create scripts/build-registry.ts with OCX Registry Protocol v1 compliance - Validate all component files exist and match expected patterns - Generate dist/registry/ output with index.json and packuments - Compute SHA-256 hashes for all files - Support --version flag for version injection - Support --validate-only flag for CI checks - Add registry:build and registry:validate npm scripts Task 6: OCX documentation - Add comprehensive OCX Registry Guide at docs/src/content/docs/guides/ocx-registry.mdx - Document individual component installation (skills, agents, commands) - Document bundle installation (all skills, all agents, all commands) - Document profile usage (standalone and OMO profiles) - Add npm vs OCX comparison table - Update README.md with OCX installation alternative - Note dual-installation behavior and bootstrap dependency
- Add registry/** and scripts/build-registry.ts to docs.yaml trigger paths - Build registry after docs:generate with version from package.json - Copy dist/registry/ to docs/dist/registry/ before gh-pages deploy - Add registry validation job to main.yaml CI pipeline - Validate registry on all PRs and pushes to ensure integrity
- Create tests/unit/registry.test.ts with 21 tests across 8 suites - Validate JSONC parsing and structure - Validate component types are valid OCX types - Validate all component files exist on disk - Validate multi-file skills list ALL files (no missing, no .DS_Store) - Validate bundle dependencies resolve correctly - Validate profile structure (required files present) - Validate no duplicate component names - Validate component naming conventions (agent-, cmd- prefixes) All 349 tests pass including 21 new registry tests.
- Add semver validation for explicit --version flag - Add git tag fallback to version resolution chain - Add try-catch around file reads in buildPackument() - Resolution order: CLI --version → git tag → package.json → 0.0.0-dev
CI workflow: - Add fetch-tags: true to checkout for git describe support - Remove jq dependency from registry build step - Let build script handle version resolution automatically Documentation: - Add Updating Components section with ocx update workflows - Add Troubleshooting section for common registry issues
- Extract validateComponentFiles helper for file existence checks - Extract assertAllFilesExist helper for path resolution validation - Extract collectDiskFiles helper for normalized file collection - Extract getComponentsByType helper for component filtering - Fix unused variable warning (noUnusedVariables) - Eliminate 5 cognitive complexity warnings (noExcessiveCognitiveComplexity) - Maintain 21 tests, 452 assertions (no logic changes)
- Update omo/ocx.jsonc registry URL - Update standalone/ocx.jsonc registry URL - Update standalone/AGENTS.md configuration example - Remove incorrect registry.fro.bot subdomain references
Add solution documentation for the 5 code review findings addressed on this branch: test complexity, semver validation, URL consistency, CI simplification, and documentation gaps.
…g concatenation - Add "Registry" to required status checks in .github/settings.yml - Convert string concatenation to template literals in build-registry.ts
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
What's New
OCX Registry (
registry/)registry.jsonc): 48 components — 11 skills, 24 agents, 9 commands, 2 bundles, 2 profilesscripts/build-registry.ts): Validates and produces OCX Registry Protocol v1 output with semver validation, git tag version resolution, and file read error handling.well-known/ocx.jsonat docs site rootDocumentation (
docs/)docs/solutions/code-quality/ocx-registry-review-fixes.mddocumenting the review fixesCI/CD (
.github/workflows/)docs.yaml)main.yaml)Tests (
tests/unit/registry.test.ts)Code Quality
Post-review fixes applied:
--versionflag with clear error messages0.0.0-devfro.bot/systematicfetch-tags: trueVerification
No changes to
src/directory. No new npm dependencies.