contribute-skill

To automate contributing local skill modifications, you can use a skill management tool that submits your changes as a pull request. It pushes local modifications to the upstream GitHub repository and integrates them into the main codebase for review.

Skill lock management in code contribution ensures that only modifications originating from the specified upstream repository are accepted. This restricts contributions to the designated source, preventing unauthorized forks from being submitted as pull requests.

Yes, you need the gh CLI and jq to submit a pull request for local skill changes. The gh CLI handles GitHub repository interactions and pull request submission, while jq is required for processing JSON data during the contribution workflow.

Yes, the skill contribution process performs security checks before submitting a pull request. These checks are executed prior to the pull request submission to prevent unauthorized actions and ensure safe integration into the main codebase.

The best way to contribute local skill modifications back to the main repository is using an automated contribution skill. It handles pushing changes, enforces skill lock management, performs security checks, and opens a pull request on the upstream GitHub repository.

You cannot use this automated pull request workflow for repositories other than GitHub. The skill contribution automation explicitly supports GitHub for source code management and relies on the gh CLI to submit pull requests to upstream repositories.