What happens if my changes are spread across multiple plugins?

If no single scope dominates the changes, the skill returns an 'ambiguous' status, allowing the calling command to prompt the user for manual selection.

Does this skill actually perform the release or tag the commit?

No, this is a diagnostic foundation skill. It identifies the scope of the release so that subsequent release tools can apply the correct versioning and tagging logic.

Can I use this skill on branches other than main?

Yes, but the skill will provide a warning if you are not on the 'main' or 'master' branch to help prevent accidental releases from development branches.

How does the skill determine the release scope?

It uses git status --porcelain to analyze file paths and applies logic that checks if 70% or more of changes occur within a specific directory, such as a plugin or variant folder.

Release Scope Detector

Name: Release Scope Detector
Author: jayteealao

byjayteealao

배포 및 DevOps

Analyzes git changes to automatically determine the appropriate release level for plugins, marketplaces, or variants.

소개

The Detect Release Scope skill streamlines software delivery by intelligently scanning a repository's current state to identify the intended release target. By evaluating modified, staged, and untracked files against specific directory patterns, it determines whether changes impact a specific plugin, the entire marketplace metadata, or platform variants. This automation prevents versioning errors and ensures that release workflows are triggered with the correct context, significantly reducing manual configuration and human error during the deployment process.

주요 기능

Automated Git status analysis using machine-readable porcelain output
Git branch validation to ensure releases originate from authorized branches
0 GitHub stars
Intelligent dominance logic to resolve primary release scope based on change volume
Ambiguity detection with confidence scoring to handle multi-scope updates
Pattern-based file categorization for plugins, marketplaces, and variants

사용 사례

Managing versioning context in multi-tenant or multi-plugin monorepos during release cycles
Automating the input for CI/CD release pipelines based on specific repository changes
Determining if a PR requires a plugin-specific version bump or a global marketplace update

소개

주요 기능

Automated Git status analysis using machine-readable porcelain output
Git branch validation to ensure releases originate from authorized branches
0 GitHub stars
Intelligent dominance logic to resolve primary release scope based on change volume
Ambiguity detection with confidence scoring to handle multi-scope updates
Pattern-based file categorization for plugins, marketplaces, and variants

사용 사례

Managing versioning context in multi-tenant or multi-plugin monorepos during release cycles
Automating the input for CI/CD release pipelines based on specific repository changes
Determining if a PR requires a plugin-specific version bump or a global marketplace update