bootstrap-issue-config

Name: bootstrap-issue-config
Availability: InStock
Author: Warp

Generate .github/issue-triage/config.json and .github/STAKEHOLDERS from existing labels and issues.

292|39|Updated Mar 17, 2026

Search Tags:#automation #github #configuration #triage #bootstrap #labels #stakeholders

Ready to run

npx skills add https://github.com/warpdotdev/oz-for-oss --skill bootstrap-issue-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bootstrap-issue-config
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/bootstrap-issue-config
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill bootstrap-issue-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate .github/issue-triage/config.json and .github/STAKEHOLDERS. Use when setting up triage automation on a new or existing repository for the first time.

Core Features & Use Cases

Discover existing labels and categorize them into area, feature, and status labels to seed triage rules.
Analyze recent issues and templates to generate or update issue-triage config and stakeholder mappings.
Create missing labels or stakeholders while preserving existing configurations.

Quick Start

Run the bootstrap-issue-config skill on a repository to create the initial .github/issue-triage/config.json and .github/STAKEHOLDERS.

Frequently Asked Questions about bootstrap-issue-config

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

FAQPage Schema

How do I bootstrap issue triage configuration for a GitHub repository?▼

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.

Can I set up issue triage automation on an existing repository without losing current labels?▼

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.

What is the best way to generate a STAKEHOLDERS file for issue triage?▼

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.

How does issue triage config discover and categorize existing GitHub labels?▼

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.

Do I need to create missing GitHub labels before bootstrapping triage config?▼

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.

When should I use an automated issue triage bootstrap tool instead of manual configuration?▼

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.