repos

Load GitHub and GitLab repository mappings from config/git-repos.yaml.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/eron1703/claude-config-loader --skill repos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repos
Source: https://github.com/eron1703/claude-config-loader/tree/main/skills/repos
Command: npx skills add https://github.com/eron1703/claude-config-loader --skill repos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load GitHub/GitLab repository information when working with git, CI/CD, or repository management.

Core Features & Use Cases

  • Centralizes repository mappings for GitHub and GitLab
  • Supports integration with CI/CD configurations
  • Use Case: Quickly review project repos and their settings to streamline collaboration

Quick Start

Load the repository mappings from git-repos.yaml to review project references.

Frequently Asked Questions about repos

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

FAQPage Schema
How do I centralize GitHub and GitLab repository mappings for CI/CD workflows?

Centralize GitHub and GitLab repository mappings by loading the config/git-repos.yaml file, which provides an up-to-date source of truth for project references during CI/CD configuration and code management. It surfaces repository settings to streamline collaboration across multiple remotes.

What is the best way to sync project references across multiple Git repositories?

Syncing project references across multiple Git repositories relies on reading the config/git-repos.yaml file. This mapping approach serves as a centralized source of truth, supporting both GitHub and GitLab remotes for faster GitOps and code management.

Does this repository mapping approach work with both GitHub and GitLab pipelines?

Yes, this repository mapping approach works with both GitHub and GitLab pipelines. It reads the config/git-repos.yaml file to surface repository information, supporting CI/CD configurations and syncing project references across both platforms without needing additional dependencies.

How do I review repository structure and settings before cloning remotes?

Review repository structure and settings before cloning remotes by loading mappings from the config/git-repos.yaml file. This provides up-to-date project references and repository information, allowing you to validate configurations for GitHub and GitLab before executing GitOps workflows.

Do I need any external dependencies to configure repository mappings for GitOps?

No external dependencies are required to configure repository mappings for GitOps. The process reads the config/git-repos.yaml file directly to surface GitHub and GitLab repository information, serving as a standalone source of truth for project references and CI/CD integration.

Why use a centralized config file for managing Git repository data?

Using a centralized config file for managing Git repository data ensures a single source of truth for project references. It streamlines collaboration by providing up-to-date mappings for GitHub and GitLab, which speeds up GitOps tasks like cloning remotes and configuring pipelines.