repo-config

Read, write, and resolve GitHub repository configurations in YAML.

6|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill repo-config-l3digitalnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-config
Source: https://github.com/L3DigitalNet/Claude-Code-Plugins/tree/main/plugins/github-repo-manager/skills/repo-config
Command: npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill repo-config-l3digitalnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the management of GitHub repository configurations, ensuring consistency and correctness across your projects by handling per-repo and portfolio-level settings.

Core Features & Use Cases

  • Configuration Management: Read, write, and resolve GitHub repository configurations.
  • Precedence Rules: Understand and apply the hierarchy of configuration sources (portfolio overrides, per-repo files, portfolio defaults, built-in defaults).
  • Validation: Ensures configuration files adhere to a defined schema, providing helpful feedback on errors.
  • Use Case: When onboarding a new project, use this Skill to ensure its .github-repo-manager.yml file is correctly set up according to your organization's standards, or to update a portfolio-wide setting that affects multiple repositories.

Quick Start

Read the repository configuration for the 'owner/name' repository.

Frequently Asked Questions about repo-config

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

FAQPage Schema
How do I manage GitHub repository configuration files across multiple projects?

You can manage GitHub repository configurations by reading, writing, and resolving settings for per-repo and portfolio levels, ensuring consistency and correctness across your projects using YAML format and schema validation.

What are the precedence rules for resolving GitHub repository configurations?

Configuration resolution applies a hierarchy where portfolio overrides take precedence over per-repo files, which override portfolio defaults, which in turn override built-in defaults to determine the effective settings.

How do I validate a .github-repo-manager.yml file against a defined schema?

Schema validation checks your YAML configuration files for correctness and adherence to defined standards, providing helpful feedback on errors to ensure your repository settings are properly set up.

Can I update a portfolio-wide GitHub setting that affects multiple repositories?

Yes, you can write and update portfolio-level configurations that act as defaults or overrides, allowing you to apply consistent settings across multiple repositories within your organization simultaneously.

What is the best way to onboard a new project with consistent GitHub repository settings?

Use this Skill to set up and validate your `.github-repo-manager.yml` file according to your organization's standards, ensuring the new project adheres to defined portfolio and per-repo configurations.