run-test-suite-after-registration-changes — Claude Code skill
The run-test-suite-after-registration-changes skill calls for running the test suite after registration edits and checking that each registration point stays in sync. Use it when changing skill files and their manifests.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill run-test-suite-after-registration-changes -a claude-codeWhat run-test-suite-after-registration-changes does
After registration changes, the skill requires running the test suite and checking that registration points agree. The checks cover bundled-skills, package.json, and smoke tests; all must be consistent and pass before the work is marked complete.
It also calls for comparing the bundled-skills manifest with the files that are actually present. A mismatch means the registration change is not ready to complete. The skill is available for Claude Code, Codex, and OpenCode.
What it helps with
- run the test suite after registration edits
- check registration entries across
bundled-skillsandpackage.json - compare the
bundled-skillsmanifest with actual files - add or update tests for the trigger condition
Example prompts for the agent
- After changing registration, check every related entry and run the test suite.
- Compare the
bundled-skillsmanifest with the files and run the smoke tests. - Add or update tests for the condition that triggers this skill.
How to install run-test-suite-after-registration-changes
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill run-test-suite-after-registration-changes -a claude-code2Manually: put the files in place
~/.claude/skills/run-test-suite-after-registration-changes/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/run-test-suite-after-registration-changes/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill run-test-suite-after-registration-changes -a codex2Manually: put the files in place
.agents/skills/run-test-suite-after-registration-changes/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill run-test-suite-after-registration-changes -a cursor2Manually: put the files in place
.cursor/skills/run-test-suite-after-registration-changes/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .opencode/skills/generated/run-test-suite-after-registration-changes2Manually: put the files in place
.github/skills/run-test-suite-after-registration-changes/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill run-test-suite-after-registration-changes -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .opencode/skills/generated/run-test-suite-after-registration-changesManually: put the files in place
.devin/skills/run-test-suite-after-registration-changes/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill run-test-suite-after-registration-changes -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about run-test-suite-after-registration-changes
How do I install run-test-suite-after-registration-changes in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill run-test-suite-after-registration-changes -a claude-code. The skill file is at ~/.claude/skills/run-test-suite-after-registration-changes/SKILL.md.
What does run-test-suite-after-registration-changes do?
It requires a test run after registration edits and checks that registration points remain consistent. Its review checks also cover smoke tests and the bundled-skills manifest.
What should I check after changing skill registration?
Make sure bundled-skills and package.json match the actual files, then confirm that the smoke tests pass.
Source text
SKILL.md · MIT
--- name: run-test-suite-after-registration-changes description: run test suite after registration changes metadata: generated_from_knowledge: '["8cc9b651-c706-405f-990f-bad337b620b8"]' source_knowledge_ids: '["8cc9b651-c706-405f-990f-bad337b620b8"]' generated_at: "2026-07-14T05:31:50.635Z" confidence: "0.60" status: active version: "1" skill_origin: generated --- <!-- generated by opencode-swarm skill-generator. Do not edit by hand; edits will be preserved on regeneration only with controlled update mode. --> # run test suite after registration changes ## Trigger - (no explicit trigger metadata; cluster derived from category/tags) ## Required Procedure - run test suite after registration changes - verify all registration points are updated together ## Forbidden Shortcuts - (none recorded) ## Delegation Template When delegating a task affected by this skill, include: ``` SKILLS: file:.opencode/skills/generated/run-test-suite-after-registration-changes/SKILL.md ``` ## Reviewer Checks - smoke tests pass - bundled-skills manifest matches actual files ## Test Engineer Checks - Add or update tests covering the trigger condition and the forbidden shortcut. ## Source Knowledge IDs - 8cc9b651-c706-405f-990f-bad337b620b8 — When restructuring skill files and updating registration across multiple points (bundled-skills, package.json, smoke tests), verify all registration points are consistent and tests pass before marking complete.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm