skills.rest
m16khb
m16khbCOMMUNITY
Explore all skills by this author →
GitHub

sharing-skills

Create branches, commit SKILL.md changes, and open pull requests to upstream.

Updated Dec 2, 2025
Search Tags:#contribution#branching#pull-request#upstream
One-click install
npx skills add https://github.com/m16khb/claude-integration --skill sharing-skills-m16khb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/m16khb/claude-integration/tree/main/.claude/skills/superpowers/sharing-skills
Command: npx skills add https://github.com/m16khb/claude-integration --skill sharing-skills-m16khb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides contributors to share broadly useful skills upstream via branches and PRs.

Core Features & Use Cases

  • Branching & PR flow: Create feature branches, push, and open PRs.
  • Documentation for review: Summaries, testing notes, and context in PR bodies.
  • Usage Scenario: Share a new skill with the broader CLAUDE community via a PR.

Quick Start

Create a feature branch, commit your skill, and open a PR to 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 the upstream repository via pull request?▼

Contributing a skill upstream requires creating a feature branch from your local clone, committing your skill with proper documentation, pushing to your fork, and opening a PR. The process ensures skills are broadly applicable, well-tested via the writing-skills TDD process, and include updated SKILL.md files before submission to the main repository.

What prerequisites do I need before sharing a skill upstream?▼

You need the gh CLI installed, a configured local skills directory at ~/.config/superpowers/skills/, and skills that have been tested using the writing-skills TDD process. Each PR should contain one skill and follow multi-skill contribution rules to maintain upstream repository quality.

How do I prepare documentation when submitting a skill as a pull request?▼

Include a summary of your skill, testing notes documenting how you validated it, and context in the PR body explaining why it's broadly useful. Ensure your SKILL.md is complete and reflects the skill's functionality, making it easy for reviewers to understand its purpose and usage.

Can I submit multiple skills in a single pull request?▼

No, the multi-skill contribution rules require one skill per PR. This ensures clarity in review, easier tracking of changes, and simpler reverting if needed. Submit each skill as a separate pull request to the upstream repository.

What's the branching workflow for sharing a skill upstream?▼

Create a feature branch from your local clone, make your changes, commit them with clear messages, push the branch to your fork, and open a PR to the upstream repository. This workflow keeps contributions organized and allows maintainers to review and merge changes systematically.

Related Skills

Explore More Content & Communication Skills→
dsifrydsifry
60

sharing-skills

Create branches, edit skills, and submit PRs to upstream repositories.

Community
Intermediate
cpfcoachingcpfcoaching

Sharing Skills

Create pull requests to contribute skills to upstream repositories.

Community
Intermediate
FradSerFradSer
577

start-release

Automates git-flow release branch creation and version bumping for software projects using git-flow-next CLI.

Community
Advanced
octodemooctodemo

make-contribution

Guides users through creating GitHub issues, branches, commits, and pull requests per repository guidelines.

Official
Intermediate