how-this-repo-works

Documents the plugin build, release, and propagation pipeline for nsheaps/ai-mktpl.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/nsheaps/ai-mktpl --skill how-this-repo-works
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: how-this-repo-works
Source: https://github.com/nsheaps/ai-mktpl/tree/main/.claude/skills/how-this-repo-works
Command: npx skills add https://github.com/nsheaps/ai-mktpl --skill how-this-repo-works

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill explains the full lifecycle and propagation path for Claude Code plugins in the nsheaps/ai-mktpl repository, making it easy to understand how source changes become installed plugin versions for users. It helps reduce confusion when version bumps, marketplace.json drift, or cache issues prevent updates from appearing in user sessions.

Core Features & Use Cases

  • End-to-end flow mapping: Describes developer edits, PR validation, CD version bumps, marketplace.json regeneration, commits, and push semantics.
  • Operational debugging: Guides investigation of detect-plugin-changes output, release-it bumps, CI/CD job behavior, and local vs GitHub marketplace differences.
  • Tooling and configuration reference: Details the roles of mise, just, yarn, release-it, GitHub Actions, plugin.json schema, and the Claude Code plugin cache.
  • Use Case: When a user reports that a plugin update is not active, follow the pipeline steps to identify whether the issue is in CI validation, version bumping, marketplace generation, or client cache resolution.

Quick Start

Explain step-by-step how a change to plugins/scm-utils in nsheaps/ai-mktpl moves from a merged PR to being served from ~/.claude/plugins/cache for end users.

Frequently Asked Questions about how-this-repo-works

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

FAQPage Schema
How does the Claude Code plugin build and release pipeline work in nsheaps/ai-mktpl?

The Claude Code plugin pipeline maps developer edits through PR validation, CD version bumps via release-it, marketplace.json regeneration, and commits to serve updates to end users. It traces source changes from merged PRs to installed plugin versions in the local cache.

Why is my Claude Code plugin update not showing up in the user session?

Plugin update failures can originate in CI validation, release-it version bumps, marketplace.json generation, or client-side cache resolution. Troubleshoot the pipeline by checking detect-plugin-changes outputs and verifying if the update propagated to ~/.claude/plugins/cache.

How do I configure release-it version bumps for GitHub Actions CD jobs?

Release-it version bumps are configured within the GitHub Actions CD jobs of the ai-mktpl repository. The pipeline uses justfile recipes to execute these bumps automatically after a PR merges, ensuring the plugin version is updated before marketplace.json regeneration.

What tools are required to run the justfile recipes for plugin marketplace generation?

Running justfile recipes for plugin marketplace generation requires the mise, just, and yarn toolchain. These tools manage the environment, execute commands, and handle dependencies needed to validate PRs and trigger the release-it versioning process.

Does the Claude Code marketplace schema differ between local and GitHub consumption?

Yes, the pipeline maps distinct semantics for local versus GitHub marketplace consumption. Understanding these differences is crucial when debugging why a plugin version appears locally but differs from the GitHub marketplace.json distribution.

How do I step through the detect-plugin-changes output in CI/CD?

To step through detect-plugin-changes output, review the CI/CD job behavior in GitHub Actions to see which plugins triggered a version bump. This output dictates whether release-it proceeds and if marketplace.json is regenerated and pushed.