sharing-skills

Automate GitHub PR review resolution by fixing comments and failing CI checks.

68|6|Updated Apr 16, 2020
One-click install
npx skills add https://github.com/zenobi-us/dotfiles --skill sharing-skills-zenobi-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sharing-skills
Source: https://github.com/zenobi-us/dotfiles/tree/main/devtools/files/opencode/skills/sharing-skills
Command: npx skills add https://github.com/zenobi-us/dotfiles --skill sharing-skills-zenobi-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? Sharing valuable internal skills or patterns with a wider team or open-source community can be complex, involving intricate Git workflows and Pull Request processes.

Core Features & Use Cases

  • Upstream Contribution Workflow: Guides through syncing main, creating feature branches, committing, and pushing to your fork.
  • Pull Request Generation: Automates the creation of well-structured Pull Requests to contribute skills to an upstream repository.
  • Multi-Skill Contribution Guidance: Enforces single-skill PRs for independent reviewability and faster merges.
  • Use Case: You've developed a new refactoring-patterns skill that significantly improves code quality. Use this Skill to properly branch, commit, push, and create a Pull Request to share it with the main skill repository, making it available to everyone.

Quick Start

Use the sharing-skills skill to contribute your new 'code-formatter' skill to the upstream repository, starting by syncing your main branch.

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 an upstream repository using Git?

Contributing a skill involves syncing your main branch, creating a feature branch, committing your changes, pushing to your fork, and opening a pull request to the upstream repository. This workflow ensures your skill is properly integrated and reviewable by maintainers before merging.

What's the best way to structure a pull request when sharing skills with a team?

Each pull request should contain a single skill to enable independent reviewability and faster merges. This approach isolates changes, simplifies review threads, and allows maintainers to merge contributions without blocking unrelated skills.

How do I resolve GitHub pull request review comments and CI check failures?

Address all unresolved review threads and failing CI checks by creating individual commits per thread and per check type, then pushing updates. Validate that all threads are resolved and checks pass before the pull request is ready to merge.

Can I automate the pull request creation process when sharing skills?

Yes, the sharing-skills workflow automates pull request generation after you've committed and pushed your changes to your fork. It handles the creation of well-structured pull requests targeting the upstream repository.

What prerequisites do I need before contributing a skill to an open-source repository?

You need a forked repository, a synced main branch with upstream changes, Git configured for commits, and your skill code ready in a feature branch. Fresh data fetched from GitHub ensures your pull request reflects the latest upstream state.

Why should I use a separate branch for each skill contribution?

Feature branches isolate your skill changes from main, enable parallel work on multiple skills, and simplify pull request management. Each branch maintains a clean history and allows independent review and merge cycles.