submit-to-extension-index

Automate 3D Slicer extension submission with validation and PR generation.

Updated Jan 25, 2026

Search Tags:#automation #git #validation #pull-request #submission #extension-index #slicer

Ready to run

npx skills add https://github.com/benzwick/SlicerMouseMaster --skill submit-to-extension-index

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: submit-to-extension-index
Source: https://github.com/benzwick/SlicerMouseMaster/tree/main/.claude/skills/submit-to-extension-index
Command: npx skills add https://github.com/benzwick/SlicerMouseMaster --skill submit-to-extension-index

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Complete workflow to submit an extension to the 3D Slicer Extension Index, reducing manual steps and ensuring validation.

Core Features & Use Cases

Automates validation of extensions before submission to catch issues early.
Guides forking, cloning, and branch creation to maintain a clean submission history.
Pre-populates the PR body using the latest template to streamline code review.

Quick Start

Run the validator to confirm readiness, then follow the guided steps to fork the repository, clone it locally, copy your extension JSON, push a branch, and open a pull request.

Frequently Asked Questions about submit-to-extension-index

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I submit a 3D Slicer extension to the Extension Index?▼

Submitting a 3D Slicer extension involves validating your extension, forking the index repository, creating a branch, copying your extension JSON, and opening a pull request. This workflow automates those steps to ensure validation and clean submission history.

Can I validate my 3D Slicer extension before opening a pull request?▼

Yes, you can validate your 3D Slicer extension before opening a pull request. The workflow runs a pre-submission validator to catch issues early, ensuring your extension meets the Extension Index requirements before you proceed with forking and branch creation.

What is the process for forking and cloning the Slicer extension index repository?▼

The process for forking and cloning the Slicer extension index repository is guided step-by-step. It handles forking the repository, cloning it locally, and creating a branch to maintain a clean submission history before you copy your extension JSON and push.

How do I create a pull request for a 3D Slicer extension submission?▼

To create a pull request for a 3D Slicer extension submission, the workflow pre-populates the PR body using the latest template. This streamlines code review by ensuring all required information is included after you push your extension branch to the forked repository.

Do I need git to automate my 3D Slicer extension submission?▼

Yes, you need git to automate your 3D Slicer extension submission. The workflow relies on git operations like forking, cloning, branch creation, and pushing to manage the end-to-end submission steps and maintain a clean submission history in the Extension Index.