mstack-setup

Name: mstack-setup
Availability: InStock
Author: abhilash-003

Generate .mstack/config.yml from detected GitHub repository conventions and labels.

3|Updated Apr 13, 2026

Search Tags:#github #release automation #issue triage #label taxonomy #configuration generation #repo setup #mstack

Ready to run

npx skills add https://github.com/Abhilash-003/mstack --skill mstack-setup

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mstack-setup
Source: https://github.com/Abhilash-003/mstack/tree/main/setup-skill
Command: npx skills add https://github.com/Abhilash-003/mstack --skill mstack-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

MStack needs a per-repository configuration (label taxonomy, triage/review/release defaults) but maintainers shouldn’t have to set it up by hand for every new repo.

Core Features & Use Cases

Detects repo conventions by scanning templates, CI/workflows, changelog format, test directories, and the default branch to tailor configuration to the repository.
Sets up missing GitHub labels by comparing existing labels against the MStack taxonomy and optionally creating any missing ones.
Writes .mstack/config.yml using detected conventions and your choices, preparing the repo for follow-on skills like triage, review, respond, and health.

Quick Start

Run mstack-setup to create .mstack/config.yml for the current repository by scanning conventions and proposing any missing label taxonomy.

Frequently Asked Questions about mstack-setup

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

FAQPage Schema

How do I automate GitHub repo setup and generate a configuration file from existing conventions?▼

Automated GitHub repo setup scans templates, CI workflows, changelog formats, and the default branch to generate a tailored .mstack/config.yml file, eliminating manual configuration for maintainers.

How do I create missing GitHub labels for a repository taxonomy automatically?▼

Creating missing GitHub labels involves comparing existing repository labels against a defined MStack taxonomy and optionally generating any absent labels to ensure consistent issue triage and categorization.

Do I need the GitHub CLI installed to configure repository release automation settings?▼

Configuring repository release automation settings requires the GitHub CLI (gh) to be installed and available, as it handles repository discovery and manages the creation of missing labels.

What is the best way to update or reconfigure an existing GitHub repository configuration when conventions change?▼

Reconfiguring an existing GitHub repository configuration is handled by rescanning repo conventions and rewriting the .mstack/config.yml file, applying targeted updates whenever the current setup is missing or incorrect.

Can I use this automated configuration approach for first-time setup on a new GitHub repository?▼

First-time setup on a new GitHub repository is fully supported by detecting conventions like test directories and changelog styles, then writing the initial .mstack/config.yml and creating missing labels.

Why does my generated repository configuration need a specific label taxonomy for issue triage?▼

A specific label taxonomy for issue triage is needed because the generated .mstack/config.yml relies on these labels to prepare the repository for follow-on skills like triage, review, respond, and health checks.