ci: auto-build hub.json and fix duplicate source validation

[runkids]

Summary

• CI auto-commits skillshare-hub.json when skills/*.json changes — contributors no longer need make build
• Fix validate.sh duplicate source check: use source + skill combo (allows skill-creator and template-skill to share anthropics/skills source)
• Simplify contributor workflow in CONTRIBUTING.md (4 steps instead of 8)
• Add category split rule: 3+ skills from same org → own file, otherwise community.json
• Remove "Ran make build" from PR template checklist

Changes

File	Change
.github/workflows/validate-pr.yml	contents: write, checkout PR branch, auto-commit step
scripts/validate.sh	Duplicate check uses source + skill combo
CONTRIBUTING.md	Simplified workflow, category split rule, file renames
.github/PULL_REQUEST_TEMPLATE.md	Removed manual build checklist item

Test plan

• CI workflow auto-commits hub.json on skill data PR
• Validate passes with multi-skill repo entries (same source, different skill field)

[gemini-code-assist]

Summary of Changes

Hello @runkids, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the developer experience and validation robustness for the skill-sharing hub. It automates the skillshare-hub.json build process within CI, freeing contributors from manual build steps. Concurrently, it refines the duplicate source validation logic to be more flexible and accurate, while also simplifying the contribution guidelines and clarifying skill categorization rules.

Highlights

• CI Automation for skillshare-hub.json: The CI pipeline now automatically builds and commits skillshare-hub.json when changes are made to skills/*.json, removing the need for contributors to run make build manually.
• Enhanced Duplicate Source Validation: The validate.sh script's duplicate source check has been updated to consider both the source and skill fields, allowing multiple skills from the same source if they have different skill identifiers.
• Streamlined Contributor Workflow: The CONTRIBUTING.md guide has been simplified, reducing the number of steps for adding a new skill from eight to four, improving the onboarding experience for new contributors.
• New Skill Category Rule: A new rule has been introduced for categorizing skills: if three or more skills originate from the same organization/author, they will receive their own dedicated JSON file; otherwise, they are added to community.json.
• PR Template Update: The "Ran make build" checklist item has been removed from the pull request template, reflecting the new automated CI process.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• .github/PULL_REQUEST_TEMPLATE.md
  • Removed the manual make build checklist item.
• .github/workflows/validate-pr.yml
  • Configured CI to auto-commit skillshare-hub.json by adding contents: write permission, checking out the PR branch, and including an auto-commit step.
• CONTRIBUTING.md
  • Revised the contribution workflow.
  • Added a new rule for skill categorization.
  • Updated file naming conventions in the categories table.
• scripts/validate.sh
  • Updated the duplicate source validation to check the combination of source and skill instead of just source.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/validate-pr.yml

Activity

• No human activity (comments, reviews, etc.) has been recorded yet for this pull request.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

No new or changed skill sources to audit.

[gemini-code-assist]

Code Review

This pull request introduces significant improvements to the contributor workflow and the validation process. Automating the skillshare-hub.json build in CI removes a manual step for contributors, making the process smoother. The updated duplicate source validation logic correctly accounts for multi-skill repositories by combining source and skill fields, which is a crucial correctness fix. Furthermore, the CONTRIBUTING.md file has been simplified and clarified with new category rules, enhancing maintainability and ease of use for new contributors. Overall, these changes are well-implemented and positively impact the project's usability and integrity.