new-repo

Creates GitHub repositories with scaffold files, registry entries, and canonical propagation wiring.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill new-repo-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-repo
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/new-repo
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill new-repo-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating a new repository by hand often skips critical setup steps like manifests, registry entries, and policy files, leaving repos disconnected from the canonical propagation system. This Skill enforces a complete, repeatable workflow so every repo is correctly wired in from day one. ## Core Features & Use Cases - Full repo creation workflow: Decides org and repo type, runs gh repo create, clones locally, and scaffolds .repo-manifest.yaml, CLAUDE.md, README.md, .gitignore, and .asae-policy. - Canonical registry integration: Adds the repo to propagation/registry.yaml in mm-claude-canonical so skills, rules, and references propagate automatically. - Job-hunt portfolio sub-flows: Handles special wiring for job-app planning hubs and portfolio-artifact spokes using funnel manifest fields (hub, parent, scope). - Use Case: When you say "create a repo for my new CLI tool", the Skill picks the right org and naming pattern, creates and scaffolds the repo, registers it for propagation, and verifies the canonical content landed. ## Quick Start Ask the assistant to create a new repo for your project, for example by saying "make a new repo for my analytics CLI", and it will walk through org selection, scaffolding, registration, and verification.

Frequently Asked Questions about new-repo

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

FAQPage Schema
How do I create a new GitHub repo with gh CLI and scaffold files?

Run gh repo create <org>/<name> --private, clone it locally, then commit the scaffold files: .repo-manifest.yaml, CLAUDE.md, README.md, .gitignore, and .asae-policy. This Skill automates that full sequence including the registry entry.

When should I not create a new repository?

Skip a new repo when adding a feature to an existing app, adding a skill or rule to the canonical repo, running a throwaway experiment, or building a sub-component without its own build cycle. Only create one for work with its own build cycle, audience, or domain.

What naming convention should a Martinez Methods repo use?

Naming depends on type and org: Martinez-Methods repos use an mm- prefix (e.g. mm-cross-product-bot), personal applications use plain kebab-case, and workspace or source-vault repos use an underscore prefix like _experiments or _job-hunt-ssot.

Does this workflow require the GitHub CLI?

Yes, the workflow relies on the gh CLI for repo creation and cloning, plus git for committing and pushing the scaffold. It also requires write access to the mm-claude-canonical repo to add the propagation registry entry.

Why does a source-vault repo need a strict-5 audit threshold?

A source-vault holds source-of-truth content like the super-resume and claims ledger that every per-job deliverable tailors from, so a defect propagates everywhere. It must set audit_threshold: strict-5 explicitly in both the manifest and .asae-policy rather than inheriting the standard-2 default.