contribute-turbo

Submit Turbo skill improvements to the upstream repository via fork or source modes.

399|31|Updated Mar 11, 2026

Search Tags:#git #skill development #pull request #github #contribute #upstream

Ready to run

npx skills add https://github.com/tobihagemann/turbo --skill contribute-turbo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contribute-turbo
Source: https://github.com/tobihagemann/turbo/tree/main/skills/contribute-turbo
Command: npx skills add https://github.com/tobihagemann/turbo --skill contribute-turbo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of contributing improvements and bug fixes for Turbo skills back to the main repository, adapting to whether you're working from a fork or directly from the source.

Core Features & Use Cases

Automated Contribution Workflow: Guides users through staging changes, crafting clear explanations, and creating pull requests or direct pushes.
Repo Mode Adaptation: Automatically adjusts the contribution method based on the user's repository configuration (fork vs. source mode).
Use Case: After refining a skill to handle a new edge case, use this skill to easily submit your tested changes back to the Turbo project maintainers.

Quick Start

Use the contribute-turbo skill to submit your recent skill changes back to the upstream repository.

Frequently Asked Questions about contribute-turbo

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

FAQPage Schema

How do I submit skill improvements back to the upstream Turbo repository?▼

Submitting skill improvements upstream involves staging changes, crafting explanations, and creating pull requests or direct pushes. The process verifies contributor status and adjusts the method based on your fork or source mode repository configuration.

What is the difference between fork and source mode when contributing to a GitHub repository?▼

The difference between fork and source mode is how changes are submitted to a GitHub repository. Fork mode routes changes through pull requests from a personal copy, whereas source mode enables direct pushes, with the workflow adapting automatically.

Do I need the gh CLI to create a pull request for skill development changes?▼

Yes, the gh CLI is required to create pull requests for skill development changes. It manages the automated contribution workflow, handling commit and push operations to ensure your changes are submitted to the upstream repository.

How does an automated contribution workflow handle pending changes?▼

An automated contribution workflow handles pending changes by reviewing them, crafting clear explanations, and executing commit and push operations. It verifies contributor status and ensures changes are submitted with appropriate context to the upstream repository.

What are the limitations of using automated scripts for upstream pull requests?▼

Limitations of using automated scripts for upstream pull requests include the strict dependency on the gh CLI and the need to conform to repository contribution guidelines. The workflow must correctly adapt to fork or source modes to execute commits successfully.