skills.rest
woodrowpearson
woodrowpearsonCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sharing-skills

Standardize branching, committing, pushing, and pull requests for upstream skill contributions.

Updated Jul 14, 2025
Search Tags:#contribution#open-source#git-workflow#pull-request#upstream#sharing-skills#workflow-guidelines
One-click install
npx skills add https://github.com/woodrowpearson/mids-hero-web --skill sharing-skills-woodrowpearson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/woodrowpearson/mids-hero-web/tree/main/.claude/skills/sharing-skills
Command: npx skills add https://github.com/woodrowpearson/mids-hero-web --skill sharing-skills-woodrowpearson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies a standardized process for contributing broadly useful skills back to an upstream repository, reducing friction and aligning expectations across teams.

Core Features & Use Cases

  • Structured contribution workflow: Branch, edit, commit, push, and create PRs in a consistent manner.
  • Quality expectations: Clear testing and documentation prerequisites to ensure upstream quality.
  • Collaborative governance: Guidelines to coordinate with maintainers and avoid conflicts.

Quick Start

Follow these steps to contribute a skill:

  • Sync your local main branch with upstream and create a feature branch.
  • Add or update the skill under the skills directory (e.g., skills/sharing-skills/SKILL.md).
  • Commit and push your changes, then open a PR against the upstream repository using your preferred tooling.

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 back to an upstream repository?▼

To contribute a skill upstream, sync your local main branch, create a feature branch, add or update the skill under the skills directory, commit, push, and open a pull request against the upstream repository.

What is the standard git workflow for open-source pull requests?▼

The standard git workflow for open-source pull requests involves branching from a synced main branch, making commits with clear documentation, pushing to your fork, and submitting a PR with testing prerequisites met to ensure clean history.

Do I need to add tests before opening a pull request for a new skill?▼

Yes, you need to add tests and documentation before opening a pull request. Meeting these quality prerequisites ensures upstream quality and aligns with maintainer expectations for predictable PRs.

What's the best way to avoid conflicts when contributing to open-source projects?▼

The best way to avoid conflicts when contributing to open-source projects is to coordinate with maintainers, sync your local main branch with upstream before branching, and follow standardized procedural guidelines for collaboration.

Where should I place new skill files in my repository?▼

You should place new skill files in the skills directory, following the pattern skills/sharing-skills/SKILL.md. This structured placement ensures maintainers can locate and review your contribution predictably.

Related Skills

Explore More Software Engineering Skills→
ahandselahandsel
1

git-pull-main

Synchronizes local Git feature branches with the remote main branch.

Community
Intermediate
buihuulocbuihuuloc

engineering-health

Generate engineering team performance reports from git commit and GitHub Pull Request data.

Community
Advanced
julianobarbosajulianobarbosa
7

Git

Automate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.

Community
Advanced
anishakodeanishakode
1

speckit-git-feature

Create git feature branches with standardized naming conventions.

Community
Intermediate