gh-repo-mirror

What this does

Given a reference repo (e.g. org/ai-workbench), produces a new repo (e.g. org/ai-skills) with:

1. Identical general settings: visibility, has_issues/projects/wiki/discussions, is_template flag (caller decides), all merge methods + commit-message/title flags, delete-branch-on-merge, allow-update-branch, allow-forking, web-commit-signoff.
2. Identical security-and-analysis: advanced_security, secret_scanning, push_protection, non_provider_patterns, ai_detection, validity_checks, dependabot_security_updates.
3. Identical classic branch protection on main.
4. Identical access: every team that has access to the reference repo is added to the new repo with the same permission (pull/triage/push/maintain/admin); direct collaborators are invited at the same permission. Default-on; pass --no-mirror-access to skip.
5. A bundled neo-brutalist GitHub Pages docs site under docs/ (or /, caller picks) with the caller's branding, empty skills[] and changes[] so content lands as you add it.
6. Custom domain wired via docs/CNAME (if provided) and HTTPS enforced once the cert is issued.

Quick start

Run the helper script with the reference repo + new repo name. It interviews for anything you don't pass: