configure-repo
Skill2 starsChanged 2 months agoMITView on GitHub
Configures the GitHub repository end to end with gh — description, topics, labels, develop branch, branch protection, merge settings and metadata. Use it when creating a new project's repo or when an existing one needs tidying up (e.g. "configure the repo", "set up the GitHub repository", "set the labels and branch protection").
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jayden-dang/skillstheir own version, first seen Aug 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jayden-dang/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- changelogSkill
- commitSkill
- copywritingSkill
- design-system-auditSkill
- i18n-paritySkill
- identitySkill
- instantiateSkill
- migration-guardSkill
- new-adrSkill
- new-specSkill
- open-issueSkill
- open-prSkill
- port-changeSkill
- prototypeSkill
- releaseSkill
- seo-auditSkill
- update-templateSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Leave the GitHub repository operational and consistent with the template.
- Very specific: line 11
Read README.md and docs/product/business-model.md to derive the description and topics.
- Very specific: line 23
Run .github/scripts/setup-labels.sh (it uses .github/LABELS.md as the catalog).
- Very specific: line 27
Create develop off main if it does not exist, publish it and set it as the repo's default branch (gh api -X PATCH repos/{owner}/{repo} -f …
- Very specific: line 31
Verify that .github/dependabot.yml has target-branch: "develop" in every ecosystem.
- Distinctive: line 64
Do three things, the moment the 403 appears:
- Very specific: line 77
Verify Actions is enabled and that the active workflows (quality.yml, secret-scan.yml) run.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Leave the GitHub repository operational and consistent with the template. It requires
an authenticated gh; verify with gh auth status before starting.
Step 1 — Context
Read README.md and docs/product/business-model.md to derive the description and
topics. Detect the current repo (gh repo view). If there is no remote, ask whether to
create it (gh repo create — public/private is the person's call).
Step 2 — Metadata
- Description: one sentence from the product's vision (
gh repo edit --description). Homepage: the product URL if there is one. - Topics: 3–6 derived from the stack and the domain (
gh repo edit --add-topic).
Step 3 — Labels
Run .github/scripts/setup-labels.sh (it uses .github/LABELS.md as the catalog).
Step 4 — Branches and flow
- Create
developoffmainif it does not exist, publish it and set it as the repo's default branch (gh api -X PATCH repos/{owner}/{repo} -f default_branch=develop) — this is not optional: the default branch is where new PRs and Dependabot's point; if it staysmain, Git Flow breaks (CONTRIBUTING.md). - Verify that
.github/dependabot.ymlhastarget-branch: "develop"in every ecosystem. - Protection for
main(anddevelopif the person wants it): PR required, no force-push, conversations resolved and required checks by their check-run name, not the workflow's:Quality(fromquality.yml) andGitleaks(fromsecret-scan.yml). If you use the workflow name, the PR waits forever for a check that never reports. Verify them withgh api repos/{owner}/{repo}/commits/{sha}/check-runs --jq '.check_runs[].name'over a commit that has already run CI. Apply viagh api repos/{owner}/{repo}/branches/{branch}/protectionand show the JSON before applying. - Check the local hooks actually run:
bash .github/scripts/check-hooks-enabled.sh(with--fixit enables them).core.hooksPathdoes not travel in the repository, so the default state of any fresh clone is "no local verification at all".
If GitHub answers 403 to the protection
gh: Upgrade to GitHub Pro or make this repository public to enable this feature. (HTTP 403)On a private repository on the free plan branch protection does not exist. This is
not a loose error to report at the end: it is an expected outcome that changes what
the project can promise. CONTRIBUTING.md and AGENTS.md declare PR required, no
direct pushes to main/develop and required checks to merge — and all of that is
enforced by the server. Without it, this is what is left:
| Control | What it covers | How it is bypassed |
git-guardrails.sh | Pushing from a protected branch | It is an agent hook: it does not apply to people |
.githooks/pre-push | The checks before publishing | git push --no-verify |
core.hooksPath | Enables the above | It gets forgotten: manual, once per clone |
Do three things, the moment the 403 appears:
- Say it plainly, without softening it: "this repository has no branch protection;
the local hooks are the only control and they are bypassed with
--no-verify". - Offer the real way out: making the repository public enables protection for free. That is a product decision, not a technical one — ask it here, not later.
- Put it in writing in the
README.mdor in the instantiation ADR, so whoever arrives later does not take as given a set of rules nobody enforces.
Step 5 — Merge settings and hygiene
- Squash merge enabled, delete branches on merge, issues enabled; the PR/issue templates already come with the repo.
- Verify Actions is enabled and that the active workflows (
quality.yml,secret-scan.yml) run.
Step 6 — Close
Summarize what was configured (with the commands you ran) and record it in the CHANGELOG
under Unreleased. And say what was NOT protected, with its consequence — listing
what failed for permissions is not enough: if there is no branch protection, the summary
has to say that the CONTRIBUTING.md rules are enforced by nobody (Step 4).
Rules: show every destructive or configuration command before running it the first time; do NOT delete existing labels/branches without confirming; do NOT touch repos other than the current project's.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

