sharing-skills

Create pull requests to contribute tested skills to an upstream repository.

4|Updated Dec 7, 2020
One-click install
npx skills add https://github.com/charly3pins/dotfiles --skill sharing-skills-charly3pins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/charly3pins/dotfiles/tree/main/.config/opencode/skills/sharing-skills
Command: npx skills add https://github.com/charly3pins/dotfiles --skill sharing-skills-charly3pins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh CLI.

What problem does it solve?

Contributing new skills to an upstream repository can be complex, involving specific Git workflows and pull request requirements, leading to errors or delays. This skill streamlines the entire contribution process.

Core Features & Use Cases

  • Streamlined Contribution: Guides through the exact steps of branching, committing, pushing, and creating pull requests for skill contributions.
  • Prerequisite Checks: Ensures your skills are well-tested and documented according to guidelines before submission.
  • PR Template Generation: Helps create well-structured pull requests with summary, testing, and context sections, increasing merge likelihood.
  • Use Case: After developing a new, broadly useful skill locally and testing it thoroughly, use this skill to correctly package and submit it as a pull request to the main skills repository.

Quick Start

I have a new skill called 'my-new-feature' that I want to share. Guide me through the process of creating a pull request to contribute it upstream.

Frequently Asked Questions about sharing-skills

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

FAQPage Schema
How do I contribute a skill to an open source repository using pull requests?

To contribute a skill via pull request, clone the skills repository locally, create a feature branch, add your well-tested and documented skill, commit with a descriptive message, push to your fork, and open a PR with a summary of changes. This workflow ensures proper review before merging upstream.

What's the correct Git workflow for submitting a new skill as a pull request?

The Git workflow involves branching from the main repository, editing or adding your skill files, committing with clear messages about what the skill does, pushing to your remote fork, and creating a pull request with testing details and context. Following these steps increases the likelihood of approval and integration.

What do I need to prepare before sharing a skill upstream?

Before contributing, ensure your skill is well-tested, fully documented according to project guidelines, and broadly useful beyond a single project. You'll also need a local clone at ~/.config/superpowers/skills/ and GitHub CLI (gh) installed to execute the contribution workflow.

Can I use GitHub CLI to streamline my skill contribution workflow?

Yes, GitHub CLI (gh) is required for this contribution workflow. It handles the pull request creation step, enabling you to submit your skill contribution directly from the command line after pushing your branch.

What happens after I create a pull request for my skill contribution?

After submitting your pull request, it enters the review process where maintainers evaluate your skill against contribution guidelines. A well-structured PR with testing documentation and clear context accelerates review and increases the chance of merge into the upstream repository.