sharing-skills

Name: sharing-skills
Availability: InStock
Author: Smooth-Operation

Standardize upstream contributions with one-skill-per-PR and branch naming conventions.

Updated Jan 7, 2026

Search Tags:#git #skills #code-review #contribute #open-source #upstream #PR workflow

Ready to run

npx skills add https://github.com/Smooth-Operation/household-expense-tracker --skill sharing-skills-smooth-operation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/Smooth-Operation/household-expense-tracker/tree/main/.claude/skills/meta/sharing-skills
Command: npx skills add https://github.com/Smooth-Operation/household-expense-tracker --skill sharing-skills-smooth-operation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps contributors share their improvements with the community by providing a clear, repeatable workflow for upstream contributions and PR hygiene.

Core Features & Use Cases

One Skill per PR: Keeps reviews focused and reduces integration risk.
Structured Workflow: Sync upstream, create feature branches, develop, test with standardized checks, and open a PR.
Governance & Clarity: Uses branch naming conventions and well-structured SKILL.md so others can reuse patterns.

Quick Start

Fork or clone the repository.
Create a new skill branch named skill/your-skill-name.
Implement the skill following the writing-skills pattern, then test with testing-skills-with-subagents.
Commit, push, and open a PR following the guidelines in this skill.

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 open source project via a PR?▼

Contributing a skill via a PR requires forking the repository, creating a branch named skill/your-skill-name, implementing the pattern, and opening a pull request. This maintains a structured workflow and disciplined PR hygiene for upstream contributions.

What is the one-skill-per-PR rule for open source contributions?▼

The one-skill-per-PR rule keeps code reviews focused and reduces integration risk by ensuring each pull request addresses a single reusable improvement pattern. This governance standard maintains clarity and disciplined PR hygiene for upstream contributions.

How do I structure an upstream contribution branch for code review?▼

Structuring an upstream contribution branch requires syncing with the upstream repository and creating a branch named skill/your-skill-name. This branch naming convention maintains governance, clarity, and disciplined PR hygiene during code review.

Do I need to write a SKILL.md file when sharing open source code?▼

Yes, writing a well-structured SKILL.md file is required when sharing open source code so others can reuse your improvement patterns. It provides governance and clarity by documenting the skill alongside the standardized PR workflow.

What is the best way to sync upstream and test skills before opening a PR?▼

The best way to sync upstream and test skills is to sync the repository, create a feature branch, develop the skill, and run standardized checks with subagents. This structured workflow ensures disciplined PR hygiene before opening an upstream pull request.