sharing-skills

Coordinates Git/GitHub workflow for contributing skills upstream via pull requests.

Updated Oct 22, 2025
One-click install
npx skills add https://github.com/franroa/chezmoi --skill sharing-skills-franroa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/franroa/chezmoi/tree/main/dot_opencode/superpowers/skills/sharing-skills
Command: npx skills add https://github.com/franroa/chezmoi --skill sharing-skills-franroa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, step-by-step process for contributing broadly useful skills back to an upstream repository. It ensures your contributions are well-tested, properly documented, and follow standard Git and GitHub workflows.

Core Features & Use Cases

  • Standardized Contribution: Guides you through branching, committing, pushing, and creating a Pull Request for skill contributions.
  • Quality Assurance: Emphasizes that skills must be well-tested using the writing-skills TDD process before sharing.
  • Multi-Skill Handling: Advises against batching multiple skills in one PR, promoting independent reviewability.
  • Use Case: After developing a new, broadly applicable skill (e.g., a new design pattern or a robust debugging technique), use this Skill to contribute it to the shared skill library, making it available to others.

Quick Start

Announce skill usage

I'm using the sharing-skills skill to contribute my new 'async-patterns' skill.

The skill will then guide you through the Git and GitHub workflow.

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 new skill to a shared repository using Git and GitHub?

Contributing a skill involves creating a feature branch, editing or adding SKILL.md documentation, committing your changes, pushing to GitHub, and opening a pull request. The sharing-skills workflow guides you through each step while enforcing prerequisites like local repository setup, gh CLI authentication, and TDD testing to ensure quality contributions.

What makes a skill ready to share upstream with the community?

A skill is ready to share when it's broadly applicable beyond a single project, includes reusable patterns or techniques, is well-tested using the writing-skills TDD process, and follows writing-skills guidelines. It should solve a generalizable problem and be thoroughly documented before submission.

How do I set up my local environment to contribute skills?

You need a local clone of the skills repository at ~/.config/superpowers/skills and authentication with the gh CLI tool. These prerequisites ensure you can branch, commit, and push changes while maintaining proper version control and pull request workflow.

Should I include multiple skills in a single pull request?

No. The sharing-skills workflow advises against batching multiple skills in one PR. Each skill should have a separate branch and pull request to maintain independent reviewability and streamline the contribution process.

What testing requirements apply before sharing a skill?

Skills must be well-tested according to the writing-skills TDD (test-driven development) process before sharing. This ensures quality and reliability of contributions added to the upstream repository.