safe-settings

Apply declarative YAML repository policy across GitHub organizations via safe-settings.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/paulnsorensen/skillz-that-grillz --skill safe-settings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safe-settings
Source: https://github.com/paulnsorensen/skillz-that-grillz/tree/main/skills/safe-settings
Command: npx skills add https://github.com/paulnsorensen/skillz-that-grillz --skill safe-settings

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Safe-settings turns slow, error-prone GitHub UI changes into consistent org-scale policy management by continuously reconciling repository settings from versioned YAML in a single admin repo.

Core Features & Use Cases

  • Org-scale settings as code: manage repo metadata, merge button behavior, security toggles, branch protection classic settings, and modern rulesets across many repositories.
  • Layered configuration model: apply org-wide baselines, then override by suborg group and finally per-repo overrides, with the deeper layer winning.
  • Guardrailed drift control: provides a reconciliation workflow via a scheduled GitHub Actions sync (or a hosted Probot path) to keep live settings aligned to YAML, including dry-run/validation behaviors.

Quick Start

Run the safe-settings workflow for your admin repo by setting the required variables and secrets on the admin repo, then trigger the safe-settings.yml workflow to perform the first full sync.

Frequently Asked Questions about safe-settings

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

FAQPage Schema
How do I manage GitHub branch protection and rulesets across multiple repositories?

You can manage GitHub branch protection and rulesets across multiple repositories by applying declarative YAML configuration through the safe-settings Probot app to continuously reconcile org-wide repository policies.

What is YAML reconciliation for GitHub org management?

YAML reconciliation for GitHub org management is continuously aligning live repository settings, including security toggles and team collaborators, from versioned YAML files stored in a single admin repo.

How do I configure layered repository settings to override org-wide policies?

You configure layered repository settings by defining org-wide baselines in .github/settings.yml, then applying suborg group overrides and per-repo overrides, with the deeper layer winning.

Can I use safe-settings to correct configuration drift in GitHub automatically?

Yes, safe-settings corrects configuration drift in GitHub by running a scheduled GitHub Actions cron workflow that performs a full-sync to align live repository settings with versioned YAML.

Do I need a GitHub Actions cron workflow to maintain org-wide settings?

Yes, you need a GitHub Actions cron workflow with a pinned safe-settings version and required app credentials to run the full-sync process that maintains your org-wide repository policy.

What are the limitations of managing GitHub policies as code with YAML?

Managing GitHub policies as code requires scaffolding an admin repo layout and configuring app credentials, meaning initial setup is complex and relies on a scheduled cron workflow rather than real-time event-driven updates.