sharing-skills

Contributing a skill involves branching from main, committing your changes, pushing to a remote branch, and creating a pull request through GitHub CLI. The sharing-skills workflow guides you through each step, ensuring your skill meets sharing guidelines: broadly useful, well-tested, documented, and follows best practices before merging upstream.

You need GitHub CLI (gh) installed, a local clone of the skills repository at ~/.config/superpowers/skills/, and your main branch synced to upstream. Your skill should be well-tested, documented, and broadly applicable—not project-specific—to qualify for contribution.

Yes. This skill streamlines collaborative contribution by enforcing Git best practices and version control discipline. It's designed for sharing generic, reusable skills with teams, removing manual Git complexity and reducing errors in the branching, commit, and pull-request process.

A shareable skill must be broadly useful rather than project-specific, thoroughly tested, well-documented, and align with writing-skills guidelines. The sharing-skills workflow guides you to evaluate these criteria before initiating the contribution process.

Yes, GitHub CLI (gh) is a required dependency for the sharing-skills workflow. It enables you to create pull requests and manage the branching workflow programmatically as part of the contribution process.