aim-setup-github-repo

Verify and standardize GitHub repository merge settings and PR rules using gh.

4|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/zccz14/AIM --skill aim-setup-github-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aim-setup-github-repo
Source: https://github.com/zccz14/AIM/tree/main/.agents/skills/aim-setup-github-repo
Command: npx skills add https://github.com/zccz14/AIM --skill aim-setup-github-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and verifies GitHub repository merge settings, PR merge behavior, and default branch protections using gh.

Core Features & Use Cases

  • Calibrate and enforce merge settings across repositories (squash merge, delete branch on merge, required linear history, allow auto-merge) to minimize manual checks.
  • Align default branch protection and CI checks with a RuleSet, ensuring required status checks map to actual workflow job names.
  • Enable squash auto-merge for selected PRs when preconditions are met, and verify blockers are addressed.

Quick Start

Run gh commands to check the current repo merge and PR settings, then apply the minimal changes to align with the target RuleSet.

Frequently Asked Questions about aim-setup-github-repo

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

FAQPage Schema
How do I enforce squash merge and linear history across GitHub repositories?

GitHub repository standardization automates verifying and patching merge settings via the gh CLI. It reads live repository state and applies minimal changes to enforce squash merge, linear history, and branch deletion upon merge.

How do I map required status checks to actual GitHub Actions workflow job names?

Required status checks are mapped by reading your workflow job names and aligning default branch protections with a defined RuleSet. This ensures CI checks match actual workflow jobs instead of generic or outdated names.

Can I enable auto-merge for pull requests using gh CLI?

Yes, you can enable squash auto-merge for selected pull requests when preconditions are met. The process verifies that merge blockers are addressed before allowing auto-merge behavior on the repository.

Do I need admin permissions to apply GitHub branch protection rulesets with gh?

Applying branch protection rulesets and patching merge settings via gh requires repository admin permissions. The process reads live repository state and enforces changes to default branch protections, which necessitates elevated access.

What is the best way to standardize PR merge settings across multiple GitHub repositories?

The best way to standardize PR merge settings is to use gh CLI to automate verification and apply a defined RuleSet across repositories. This minimizes manual checks by enforcing consistent merge behaviors and required CI checks.

Why are my GitHub required status checks failing to enforce on the default branch?

Required status checks may fail to enforce if the check names do not match actual workflow job names. The standardization process maps required checks directly from workflow jobs to ensure branch protections match live CI configurations.