gh-repo-setup
An OpenClaw agent skill for standardizing GitHub repository settings.
This skill is triggered conversationally — tell your OpenClaw agent to set up a repo:
Set up repo settings and branch protection for colmena/my-new-repoThe agent reads the skill instructions, inspects the repo, and applies the settings via the GitHub API. No CLI command needed — it’s a skill the agent follows, not a script you run.
What it does
Section titled “What it does”Guides an AI agent through repo setup and optimization:
- Metadata — description, homepage URL, and topics for discoverability
- Repo settings — auto-delete branches, squash merge, linear history
- Branch protection — rulesets that apply to everyone, including admins
Settings applied
Section titled “Settings applied”Metadata
Section titled “Metadata”- Description with emoji, under 100 chars
- Homepage URL pointing to deployed site
- Topics for framework, language, and domain
Merge behavior
Section titled “Merge behavior”- Squash merge as primary (PR title → commit title)
- Rebase merge allowed as alternative
- Merge commits disabled — linear history
- Auto-delete head branches after merge
Branch protection (via rulesets)
Section titled “Branch protection (via rulesets)”- No direct pushes to main — PRs required for everyone
- 1 approving review required
- Stale reviews dismissed on new pushes
- Unresolved review threads block merge
- No force push or branch deletion on main
- No bypass actors — rules apply to admins too
Why rulesets over legacy branch protection?
Section titled “Why rulesets over legacy branch protection?”GitHub rulesets are the newer API and apply universally — they can’t be bypassed by admins, support more granular conditions, and stack with other rulesets.