skills.rest
nimeshgurung
nimeshgurungCOMMUNITY
Explore all skills by this author →
GitHub

sharing-skills

Guide contributing developed skills to an upstream repository via GitHub CLI pull requests.

1|Updated Nov 17, 2025
Search Tags:#git#skill development#contribution#version control#pull request#github
One-click install
npx skills add https://github.com/nimeshgurung/artifact-hub-collections --skill sharing-skills-nimeshgurung
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/nimeshgurung/artifact-hub-collections/tree/main/skills/raw/obra/superpowers/skills/sharing-skills
Command: npx skills add https://github.com/nimeshgurung/artifact-hub-collections --skill sharing-skills-nimeshgurung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of contributing your developed skills back to a central repository, ensuring consistency and proper version control.

Core Features & Use Cases

  • Guided Workflow: Provides step-by-step instructions for branching, committing, pushing, and creating pull requests.
  • Best Practices: Emphasizes best practices like single-skill PRs and proper commit messaging.
  • Use Case: After developing a new, broadly useful skill, follow this guide to safely and effectively submit it for review and inclusion in the main project.

Quick Start

Follow the steps in this skill to create a feature branch, commit your skill changes, and push them to your fork.

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 upstream repository via a pull request?▼

To contribute a skill via a pull request, you create a feature branch, commit your changes, push them to your fork, and use the GitHub CLI to submit the PR for review.

What's the best way to prepare a skill for a GitHub pull request submission?▼

The best way to prepare a skill for a pull request is ensuring it is broadly useful, well-tested, and follows the upstream repository's contribution guidelines before branching and committing.

Do I need to create a single pull request for each skill I contribute?▼

Yes, you should create single-skill pull requests. This best practice ensures maintainers can review each skill independently and maintain proper version control consistency.

How does version control branching work when contributing developed skills?▼

Version control branching for skill contribution involves creating an isolated feature branch from your fork, committing changes there, and pushing that specific branch to trigger the pull request workflow.

Can I use the GitHub CLI to create pull requests for skill contributions?▼

Yes, you can use the GitHub CLI to create pull requests for skill contributions. It guides you through pushing your committed feature branch from your fork directly to the upstream repository.

Why should I follow contribution guidelines before submitting a skill upstream?▼

Following contribution guidelines before submitting a skill upstream ensures your pull request meets quality standards, passes review checks, and maintains consistency within the central repository's version control.

Related Skills

Explore More Software Engineering Skills→
Tx1207Tx1207
5

project-creator

Create a new project from a template, initialize uv, and configure a local Git repository.

Community
Advanced
baphledbaphled
1

pr-monitor

Monitor pull request status, CI checks, and review feedback via GitHub CLI.

Community
Intermediate
adamayoungadamayoung
1

pr

Automate pull request rebasing, local validation, and submission via git and gh CLI.

Community
Advanced
hw-native-syshw-native-sys
30

ptoas-publish-pr

Publish scoped PTOAS changes as a draft GitHub pull request.

Official
Advanced