github-repos

Configure GitHub repository settings and enforce branch protection rules via the gh CLI.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/shellicar/skills --skill github-repos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-repos
Source: https://github.com/shellicar/skills/tree/main/skills/github-repos
Command: npx skills add https://github.com/shellicar/skills --skill github-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually configuring GitHub repository settings and branch protection is error‑prone and time‑consuming, leading to inconsistent merge methods, unsecured branches, and missed code‑scanning requirements.

Core Features & Use Cases

  • Detects the appropriate convention for a repository.
  • Retrieves current repository settings and compares them with the desired configuration.
  • Applies changes to repository options, merge methods, auto‑merge, and default branch.
  • Manages rulesets for branch protection, code scanning, and pull‑request requirements.
  • Supports bulk management across multiple repositories for an organization.

Quick Start

Ask the github-repos skill to align a repository’s settings with the defined convention.

Frequently Asked Questions about github-repos

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

FAQPage Schema
How do I automate GitHub repository settings and branch protection rules?

Automate GitHub repository settings and branch protection by using convention-driven rulesets to apply merge methods, auto-merge options, and pull-request requirements across targeted repositories via the gh CLI.

What is the best way to apply consistent branch protection rules across multiple GitHub repositories?

Apply consistent branch protection across multiple GitHub repositories by detecting the appropriate convention, comparing current settings, and bulk managing rulesets for code scanning and pull-request requirements within an organization.

How does convention-driven merge method configuration work for GitHub repositories?

Convention-driven merge method configuration works by retrieving current GitHub repository settings, comparing them with the desired convention, and applying changes to merge methods, auto-merge options, and the default branch.

Can I bulk manage GitHub rulesets and code scanning requirements for an entire organization?

Yes, you can bulk manage GitHub rulesets and code scanning requirements for an entire organization by applying convention-driven configurations across multiple targeted repositories using the gh CLI with write permissions.

Do I need GitHub CLI access to configure repository settings and enforce branch protection?

Yes, you need GitHub CLI access with repository write permissions to read and modify GitHub repository settings, enforce branch protection rulesets, and apply convention-driven merge methods via API calls.

Why does manually configuring GitHub branch protection lead to inconsistent merge methods?

Manually configuring GitHub branch protection leads to inconsistent merge methods because it is error-prone and time-consuming, often resulting in unsecured branches, missed code-scanning requirements, and varied repository settings.