add-community-extension

Process GitHub issue submissions to add community extensions to the Spec Kit catalog.

Updated May 11, 2026
One-click install
npx skills add https://github.com/richardnguyen0715/keep-it-real --skill add-community-extension
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-community-extension
Source: https://github.com/richardnguyen0715/keep-it-real/tree/main/refer-projects/spec-kit/.github/skills/add-community-extension
Command: npx skills add https://github.com/richardnguyen0715/keep-it-real --skill add-community-extension

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, spec-kit-repo, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of adding new community extensions to the Spec Kit catalog, reducing manual work and ensuring consistency across the catalog.

Core Features & Use Cases

  • Automated Extension Addition: Processes GitHub issue submissions to add new extensions to the Spec Kit catalog.
  • Validation: Validates extension submissions against predefined rules.
  • Catalog Update: Updates extensions/catalog.community.json and docs/community/extensions.md with the new extension information.
  • PR Creation: Generates Pull Requests to the Spec Kit repository for review.
  • Use Case: For developers and maintainers of the Spec Kit who want to automate the process of adding new community extensions to the Spec Kit catalog.

Quick Start

To add a new extension, run the skill with the GitHub issue URL or number for the extension submission.

Frequently Asked Questions about add-community-extension

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate adding community extensions to the Spec Kit catalog?

Automating community extension additions requires processing GitHub issue submissions, validating the data against predefined rules, updating the catalog files, and generating a Pull Request to the Spec Kit repository for maintainer review.

How does Pull Request automation work for Spec Kit extension submissions?

Pull Request automation for Spec Kit works by parsing GitHub issue submissions, validating the extension data against predefined rules, updating catalog and documentation files, and automatically opening a PR for maintainer review.

Do I need GitHub API access to manage Spec Kit community contributions?

Yes, GitHub API access is required to manage Spec Kit community contributions. It enables reading incoming GitHub issue submissions and automatically creating Pull Requests to the Spec Kit repository for maintainer review.

What files are updated when adding a new extension to the Spec Kit catalog?

When adding a new extension to the Spec Kit catalog, the files `extensions/catalog.community.json` and `docs/community/extensions.md` are updated with the new extension information before a Pull Request is created.

Can I validate GitHub issue submissions before creating a Pull Request?

Yes, GitHub issue submissions are validated against predefined rules before a Pull Request is created. This ensures extension data consistency and compliance before the Spec Kit catalog files are updated.

What are the limitations of automating Spec Kit extension management?

The limitations of automating Spec Kit extension management include strict dependencies on GitHub API access and Spec Kit repository permissions, meaning the automated workflow will fail if either connection is blocked, unauthorized, or misconfigured.