Run any Skill in Manus with one click

repo-init

Stars2

Forks0

UpdatedMay 30, 2026 at 01:27

End-to-end repo bootstrap: creates the GitHub repo (gh repo create), adds an Apache-2.0 LICENSE, dispatches to scaffold-project for CI/release/config, invokes community-health, writes a README, sets topics/description, and makes the initial commit and push. Use when starting a brand-new project from zero and you need the GitHub repo, metadata, and first push handled, not just local files. Do NOT use to scaffold files inside an existing repo; invoke scaffold-project directly for that.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

urmzd

urmzd/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	repo-init
description	End-to-end repo bootstrap: creates the GitHub repo (gh repo create), adds an Apache-2.0 LICENSE, dispatches to scaffold-project for CI/release/config, invokes community-health, writes a README, sets topics/description, and makes the initial commit and push. Use when starting a brand-new project from zero and you need the GitHub repo, metadata, and first push handled, not just local files. Do NOT use to scaffold files inside an existing repo; invoke scaffold-project directly for that.
allowed-tools	Read, Grep, Glob, Bash(git ), Bash(gh ), Edit, Write
user-invocable	true
arguments	[{"name":"name","description":"Repository name","required":true},{"name":"lang","description":"Language/type: rust, go, python, node, terraform","required":false},{"name":"description","description":"One-line repo description","required":false},{"name":"visibility","description":"public or private (default: public)","required":false}]

Repo Init

Bootstrap a complete repository from zero to pushed.

Steps

Create GitHub repo: gh repo create <name> --<visibility> --description "<description>" --clone (default public).
Add LICENSE: Create an Apache-2.0 LICENSE file in the repo root.
Scaffold: If a language is specified, invoke scaffold-project (which dispatches to scaffold-<lang>) to produce:
- CI workflow (.github/workflows/ci.yml) and release workflow (.github/workflows/release.yml); see setup-ci.
- sr.yaml for semantic release; see sync-release.
- Task runner native to the language (npm scripts, Makefile, cargo, justfile for Python).
- .envrc via the setup-devenv direnv pattern (vanilla direnv + per-language version manager, not a Nix dev shell).
- Language-specific config (Cargo.toml, go.mod, pyproject.toml, package.json, etc.).
Community health: Invoke community-health to add CODE_OF_CONDUCT.md, SECURITY.md, .github/pull_request_template.md, and .github/ISSUE_TEMPLATE/ (bug report, feature request, config). Substitute {OWNER}, {REPO}, {CURRENT_MAJOR}, and {CHECK_COMMAND} placeholders. For a brand-new pre-1.0 project, set {CURRENT_MAJOR} to 0 and rewrite the SECURITY.md supported-versions table to 0.x Yes / < 0.x No.
README: Generate a README with the repo name, description, and standard badge layout.
Set metadata: gh repo edit --add-topic <topics> --description "<description>" with relevant topics for the language/type.
Initial commit and push:
- git add -A (safe here since it's a brand new repo)
- git commit -m "chore: initial project scaffold"
- git push -u origin main
Report: Show the repo URL.

Rules

Default to Apache-2.0 license.
Default to public visibility.
If no language is specified, create a minimal repo with just LICENSE, README, and .gitignore.
Use conventional commits for the initial commit.

More from this repository

same repository

asd-ste100

urmzd/dotfiles

Write or rewrite text in ASD-STE100 Simplified Technical English (STE): the approved-word dictionary discipline, controlled verb forms, sentence and paragraph limits, procedural vs descriptive rules, and safety-instruction structure. Use when the user asks for Simplified Technical English, STE, ASD-STE100, controlled language, or aerospace-style technical writing, or when authoring procedures, maintenance instructions, or safety warnings that must be unambiguous. Do NOT use for general documentation cleanup (use clean-docs), README structure (use write-readme), or ordinary prose style.

2026-07-242

agent-design-doctrine

urmzd/dotfiles

House doctrine for designing LLM agent systems: safety enforced by the harness and tools rather than model goodwill, tools that execute and return results, minimal loop code, interface-first component seams, typed config, deterministic evals over LLM judges, and POC scope discipline. Use when designing or reviewing any agent, tool-use loop, eval harness, or agent-backed CLI, in any framework. Do NOT use for Pydantic AI framework mechanics (use building-pydantic-ai-agents), generic design principles (use review-design), or Go agent-loop implementation details (use agent).

2026-07-172

manage-detect-secrets

urmzd/dotfiles

Operate the detect-secrets pre-commit hook correctly: update the baseline with the right flags, break the "baseline file was updated, please git add" commit loop, allowlist false positives, and audit real findings. Use when a commit fails on detect-secrets, the .secrets.baseline keeps changing, or a false positive blocks a push. Do NOT use for storing or injecting secrets via 1Password (use manage-secrets) or repo-wide leak scanning with gitleaks and trufflehog (use audit-security).

2026-07-172

run-eval-harness

urmzd/dotfiles

Run a project's own eval suite end to end without babysitting: locate the harness, launch it in the background, monitor to completion, parse the report into a normalized summary (pass rate, latency percentiles, tokens, cost), and diff against the previous run with per-case regressions explained. Use when asked to "run the evals", re-run after a change, or score a new dataset in any repo with an eval harness. Do NOT use for the GAP benchmark suite (use run-evals), SAIGE provider-boundary checks (use verify), or designing new eval sets (that is authoring work, not a run).

2026-07-172

triage-dotfiles-env

urmzd/dotfiles

Playbook of known failure modes in this dotfiles stack: pipx "bad interpreter" after Python rebuilds, gpg commit-signing failures, direnv/nix shellHook running bash instead of zsh, Powerlevel10k instant-prompt warnings, and Neovim plugin errors from removed Lua APIs. Use when a shell startup error, git signing failure, broken CLI shim, or nvim stack trace appears on this machine. Do NOT use for generic runtime debugging in projects (use diagnose-runtime), chezmoi naming and templating conventions (use dotfiles), or authoring pinned installers (use setup-devenv-with-chezmoi).

2026-07-172

clean-docs

urmzd/dotfiles

Clean and modernize documentation in place. Enforce no em dashes, readable structure, proper Markdown formatting, accurate commands, current examples, resolved internal links, and user-focused guidance. Use when the user invokes /clean-docs, asks to clean docs, make docs up to date, improve README/AGENTS prose, remove AI-looking punctuation, or make docs easier for users to act on.

2026-07-122

name	repo-init
description	End-to-end repo bootstrap: creates the GitHub repo (gh repo create), adds an Apache-2.0 LICENSE, dispatches to scaffold-project for CI/release/config, invokes community-health, writes a README, sets topics/description, and makes the initial commit and push. Use when starting a brand-new project from zero and you need the GitHub repo, metadata, and first push handled, not just local files. Do NOT use to scaffold files inside an existing repo; invoke scaffold-project directly for that.
allowed-tools	Read, Grep, Glob, Bash(git ), Bash(gh ), Edit, Write
user-invocable	true
arguments	[{"name":"name","description":"Repository name","required":true},{"name":"lang","description":"Language/type: rust, go, python, node, terraform","required":false},{"name":"description","description":"One-line repo description","required":false},{"name":"visibility","description":"public or private (default: public)","required":false}]

Repo Init

Bootstrap a complete repository from zero to pushed.

Steps

Create GitHub repo: gh repo create <name> --<visibility> --description "<description>" --clone (default public).
Add LICENSE: Create an Apache-2.0 LICENSE file in the repo root.
Scaffold: If a language is specified, invoke scaffold-project (which dispatches to scaffold-<lang>) to produce:
- CI workflow (.github/workflows/ci.yml) and release workflow (.github/workflows/release.yml); see setup-ci.
- sr.yaml for semantic release; see sync-release.
- Task runner native to the language (npm scripts, Makefile, cargo, justfile for Python).
- .envrc via the setup-devenv direnv pattern (vanilla direnv + per-language version manager, not a Nix dev shell).
- Language-specific config (Cargo.toml, go.mod, pyproject.toml, package.json, etc.).
Community health: Invoke community-health to add CODE_OF_CONDUCT.md, SECURITY.md, .github/pull_request_template.md, and .github/ISSUE_TEMPLATE/ (bug report, feature request, config). Substitute {OWNER}, {REPO}, {CURRENT_MAJOR}, and {CHECK_COMMAND} placeholders. For a brand-new pre-1.0 project, set {CURRENT_MAJOR} to 0 and rewrite the SECURITY.md supported-versions table to 0.x Yes / < 0.x No.
README: Generate a README with the repo name, description, and standard badge layout.
Set metadata: gh repo edit --add-topic <topics> --description "<description>" with relevant topics for the language/type.
Initial commit and push:
- git add -A (safe here since it's a brand new repo)
- git commit -m "chore: initial project scaffold"
- git push -u origin main
Report: Show the repo URL.

Rules

Default to Apache-2.0 license.
Default to public visibility.
If no language is specified, create a minimal repo with just LICENSE, README, and .gitignore.
Use conventional commits for the initial commit.