manage-repos

Apply GitHub repository defaults and strict branch review rules across repos and organizations.

12|2|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/osolmaz/tools --skill manage-repos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-repos
Source: https://github.com/osolmaz/tools/tree/main/agents/skills/manage-repos
Command: npx skills add https://github.com/osolmaz/tools --skill manage-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and harden GitHub repositories by applying safe defaults and strict merge-review rules across repos and organizations.

Core Features & Use Cases

  • Apply github-sane-defaults to every repository you create or manage, including organization-wide application with --all.
  • Enforce strict merge review and branch rules to prevent accidental merges and align with governance.
  • Provide onboarding and auditing guidance, including adding AGENTS.md, slophammer configuration, and CI integration.

Quick Start

Ask me to apply github-sane-defaults to OWNER/REPO or to all repos in an organization.

Frequently Asked Questions about manage-repos

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

FAQPage Schema
How do I enforce strict merge review and branch rules across GitHub repositories?

To enforce strict merge reviews across GitHub repositories, you can apply standardized configurations that codify branch rules and required reviews. This approach prevents accidental merges and aligns repositories with governance workflows.

Can I apply safe repository defaults to an entire GitHub organization at once?

Yes, you can apply safe repository defaults to an entire GitHub organization at once. Using organization-wide application with the --all flag ensures standardized and safe configurations are enforced across all managed repositories simultaneously.

What is the best way to audit GitHub repositories for safe defaults and onboarding configurations?

The best way to audit GitHub repositories for safe defaults is to run an auditing workflow that verifies the application of standardized configurations. This includes checking for required branch rules, AGENTS.md files, and CI integration.

How do I integrate slophammer configuration and CI into my GitHub repository auditing workflow?

To integrate slophammer configuration and CI into your auditing workflow, you apply repository defaults that codify the necessary CLI/API steps. This ensures onboarding tasks and CI integration are standardized across the repositories.

Does this GitHub repository management approach work for both individual repos and organization-wide governance?

Yes, this GitHub repository management approach works for both individual repositories and organization-wide governance. It applies safe defaults and strict merge-review rules to scale standardized configurations across different scopes.