sharing-skills

Contributing a skill involves syncing with upstream, creating a dedicated branch, developing and testing your skill with testing-skills-with-subagents, writing clear commit messages following writing-skills patterns, and submitting a focused pull request. The sharing-skills workflow enforces one skill per PR to maintain quality control and ensure community review.

The standardized workflow guides you through syncing your fork, branching for isolated development, building and testing your skill, committing with descriptive messages, pushing to your fork, and creating a pull request. This ensures contributions meet high standards and follow community patterns for widespread adoption.

Yes, testing is mandatory. You must validate your skill using testing-skills-with-subagents and ensure it adheres to writing-skills patterns. This quality assurance step is enforced before PR submission to guarantee contributions meet community standards.

No, the sharing-skills workflow enforces a one-skill-per-PR policy. This applies to new skills, updates to existing skills, and documentation changes, ensuring focused review, easier collaboration, and cleaner version history.

Contributions must follow writing-skills documentation patterns, pass testing-skills-with-subagents validation, contain non-proprietary content, include clear documentation, provide realistic examples, and have properly aligned metadata. The sharing-skills workflow ensures all contributions satisfy these quality gates.

The sharing-skills skill guides you through syncing your fork with the upstream repository before creating your branch, ensuring your contribution builds on the latest codebase and minimizes merge conflicts during community review.