repo-manager

Assess GitHub repository health and enforce tier-based policies.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh-manager.js, ensure-deps.sh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of assessing and maintaining the health and security of GitHub repositories, ensuring they adhere to best practices and owner preferences.

Core Features & Use Cases

  • Automated Health Checks: Assesses repository configuration, security posture, and adherence to defined tiers.
  • Guided Onboarding: Ensures necessary dependencies, authentication (PAT), and labels are configured correctly for new or existing repositories.
  • Tiered Management: Adapts its interaction and mutation strategy based on the repository's tier (Docs Only, Runnable Code, Public No Releases, Public Releases).
  • Use Case: A developer can use this Skill to quickly onboard a new open-source project, ensuring it has the correct branch protection rules, labels, and a valid PAT configured, before making any changes.

Quick Start

Use the repo-manager skill to assess the health of the 'my-org/my-repo' repository.

Frequently Asked Questions about repo-manager

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

FAQPage Schema
How do I automate GitHub repository health checks and enforce security policies?▼

Automate GitHub repository health checks by assessing configuration, security posture, and tier-based policies. This tool evaluates branch protection rules, dependency setups, and label management to ensure your repositories adhere to DevOps best practices and owner preferences.

What is the best way to onboard a new GitHub repository with correct branch protection and labels?▼

The best way to onboard a GitHub repository is through guided configuration that enforces tier-based policies. It automates dependency checks, PAT authentication, and label management while classifying the repository into tiers like Docs Only or Runnable Code.

How does tier-based management work for GitHub repositories?▼

Tier-based management adapts mutation strategies by classifying repositories into Docs Only, Runnable Code, Public No Releases, or Public Releases tiers. This classification tailors security enforcement, configuration automation, and interaction based on the repository's specific type.

Do I need a Personal Access Token to manage GitHub repository configurations?▼

Yes, a Personal Access Token (PAT) is required for authentication. Guided onboarding ensures necessary dependencies and a valid PAT are configured correctly before assessing repository health or applying any automated configuration changes.

Are automated GitHub repository mutations applied without my approval?▼

No, all repository mutations require explicit owner approval. The Skill operates via a conversational interface to assess health and enforce tier-based policies, ensuring you maintain complete control over any configuration changes applied to your repositories.