repo-create

Create GitHub repositories in the OgenticAI org with registry updates and bootstrap handoff.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/OgenticAI/ogentic-shield --skill repo-create-ogenticai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-create
Source: https://github.com/OgenticAI/ogentic-shield/tree/main/.claude/skills/repo-create
Command: npx skills add https://github.com/OgenticAI/ogentic-shield --skill repo-create-ogenticai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a new GitHub repository involves many error-prone manual steps: naming validation, org policy checks, team access grants, registry bookkeeping, and factory installation. This Skill orchestrates the entire repo creation workflow with a single human approval gate before any irreversible side effects. ## Core Features & Use Cases - Guided intake and validation: Collects repo name, stack, kind, visibility, license, and team access, then checks for name collisions, org policy conflicts, and stale registry entries before drafting. - Approval-gated execution: Posts a full draft plan to chat and halts until explicit approval, then creates the repo via gh, sets topics and team permissions, and pushes an initial commit. - Registry and bootstrap chaining: Updates .claude/registry/repos.yml via a PR, hands off to repo-bootstrap to install the factory, and schedules branch protection with harden-repo.py once CI has run. - Use Case: An operator says "Carve out audit-rs as its own OSS repo." The Skill drafts the plan, waits for approval, creates the public Apache-2.0 repo, registers it, and bootstraps the factory inside it. ## Quick Start Ask the agent to create a new GitHub repository named audit-rs in the OgenticAI org and approve the draft plan when prompted.

Frequently Asked Questions about repo-create

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

FAQPage Schema
How do I create a new GitHub repository with the gh CLI?▼

Run gh repo create with the org name, visibility flag, description, and license, then PATCH repo settings via gh api for wiki, projects, and auto-merge. This Skill wraps those calls in a validated, approval-gated workflow.

How to automate GitHub repo creation with approval gates?▼

Draft the full repo plan in chat first, then require an explicit approval command before any gh call executes. The Skill halts on name collisions, org policy conflicts, or stale registry entries even in bulk-approved mode.

Does this Skill support bulk repository creation?▼

Yes, a --bulk-approved mode exists for fleet-onboarding orchestrators, where an earlier phase approval substitutes for the checkpoint. Validation failures still halt execution, and the flag is ignored if it comes from a free-form operator request.

Why does repo creation fail with a 422 error on forking settings?▼

The OgenticAI org disallows forking on private repos by policy, so including allow_forking in the PATCH call returns a 422. The Skill omits that field and warns operators who request it for private repos.

When should branch protection be applied to a new repository?▼

Branch protection is applied only after CI has run on real merged PRs, because a new repo has no check names to require. The harden-repo.py script learns required checks from recent merged PRs and refuses to create protection that requires nothing.

What are the limitations of this repo creation workflow?▼

It does not handle repo renames, transfers, forks, or archival, and it does not create Linear projects. Those are handled by direct gh commands or the project-planner skill respectively.