bootstrap-issue-config

To bootstrap issue triage configuration, run this Skill on a repository to analyze existing issues, labels, and contributors, which generates the `.github/issue-triage/config.json` and `.github/STAKEHOLDERS` files automatically.

Yes, you can set up triage automation on existing repositories while preserving current configurations. The tool reads existing labels and issues, merges findings into the config, and creates CODEOWNERS-style stakeholders without overwriting your current entries.

The best way to generate a STAKEHOLDERS file is to automate it by analyzing repository contributors and recent issues. This Skill creates a CODEOWNERS-style stakeholder mapping that integrates with your issue triage configuration.

Issue triage config discovery works by reading your repository's existing labels and categorizing them into area, feature, and status labels to seed the triage rules within the generated `config.json` file.

No, you do not need to create missing labels beforehand. The bootstrap process analyzes recent issues and templates to identify missing labels or stakeholders and creates them while preserving your existing configurations.

You should use an automated bootstrap tool when setting up triage automation on a new or existing repository for the first time, allowing you to generate a comprehensive `config.json` and stakeholder mapping without manual data entry.