菜单
This skill should be used when the user asks to "set up a repo", "create a GitHub repo", "initialize git", "create a remote repository", "push to GitHub", "log in to GitHub", "gh auth", "set up GitHub", or asks about initializing a local and remote repository and pushing it to GitHub.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | repo-setup |
| description | This skill should be used when the user asks to "set up a repo", "create a GitHub repo", "initialize git", "create a remote repository", "push to GitHub", "log in to GitHub", "gh auth", "set up GitHub", or asks about initializing a local and remote repository and pushing it to GitHub. |
Initialize a local git repository and create a matching remote on GitHub using the GH CLI, with device-code authentication that works reliably in all environments.
The computer-setup skill must have been run first — it installs gh and git.
A GitHub account is required before proceeding. If the user does not have one, guide them through account creation:
Recommend enabling two-factor authentication after sign-up. For more details, see Creating an account on GitHub.
Run gh auth status — interpret whether it shows the user as authenticated.
If not authenticated, run:
GH_FORCE_TTY=1 NO_COLOR=1 GH_PROMPT_DISABLED=1 gh auth login --hostname github.com --git-protocol https --scopes "repo,read:org,workflow" > /tmp/gh-auth.log 2>&1 & sleep 3 && cat /tmp/gh-auth.log
Retrieve the one-time code from the output and display it very prominently to the user along with the URL https://github.com/login/device. For example:
GitHub login required!
Your one-time code is:
XXXX-XXXXOpen https://github.com/login/device in your browser and enter the code.
Ask the user to complete the browser authorization and confirm when done.
After the user confirms, verify:
gh auth status
Before running the init script, check if a remote is already configured:
git remote get-url origin 2>/dev/null
If origin is already set, the repo is fully configured — do not ask the
user for a name or visibility, and skip the init script entirely.
If no remote is configured, ask the user for:
private (default) or public.Then run the init script. It is bundled with this skill at scripts/repo-init.sh,
relative to the directory this SKILL.md lives in — locate it from the skill's own
directory (not your current working directory) and run it with bash:
bash <this-skill-dir>/scripts/repo-init.sh <repo-name> [private|public]
The script will:
.git/ does not existorigin is already configured locallyorigin and pushprivate), add it as origin, and pushIf finer control is needed, run each step individually:
# Initialize local repo
git init
# Create remote and link it (from the project directory)
gh repo create <repo-name> --private --source=. --remote=origin --push
gh auth status fails.--web flag for gh auth login — it attempts to open a browser
which may not work. The device code flow (default when --web is omitted) is
more reliable.scripts/repo-init.sh — Initializes local git repo and creates the matching GitHub remote in one stepThis skill should be used when the user asks to "deploy to Locaweb Cloud", "set up GitHub Actions deployment workflows", "create a preview environment", "add a production environment", "tear down an environment", "configure a custom domain", "connect to the database", "check deployment logs", "scale the VM", "recover from snapshots", "disaster recovery", "what is the app URL", "what is the deployed URL", "where is my app", or asks about architecture decisions (monolith vs microservices, vertical vs horizontal scaling), platform constraints (Postgres only, single container, port 80), managing secrets and environment variables, Dockerfile requirements, database migrations, or performing operations and troubleshooting on live infrastructure (SSH access, container logs, health checks).
This skill should be used at the very start of every session and when the user asks to "check my environment", "run a pre-flight check", "validate setup requirements", "is my system ready", or before any cofounder project initialization. It verifies the working directory, dev tools, git state, and remote configuration.
Go + React full-stack architecture with iterative local development. Use this skill when scaffolding a new app, adding features, fixing bugs, running the local dev loop, or when the user asks to "run the app locally", "run the app on my computer", "start the app", "rodar o programa", "rodar o app", "executar localmente", or any equivalent request to launch the application in their local environment. Covers project layout, database migrations, sqlc code generation, local Supabase/Postgres via Podman, Postgres extensions (pgmq, pg_cron, pgroonga, pgvector, pg_jsonschema, LISTEN/NOTIFY), and the write-test-repeat feedback cycle.
The cofounder's core operating instructions — persona, session-startup procedure, development and deployment workflows, the skill reference, and the standing rules. The project's AGENTS.md points here; invoke this skill at the very start of every session and follow it for the entire session.
This skill should be used when the user asks to "install the cofounder", "set up the cofounder in this project", "instalar o cofundador", or invokes `/cofounder:install`. It injects the cofounder instructions into the project's AGENTS.md (referenced from CLAUDE.md) and configures `.claude/settings.json`.
This skill should be used when the user asks to "set up my computer", "install dev tools", "set up mise", "set up podman", "install Homebrew", "set up development environment", "install node", "install go", or needs to ensure all development prerequisites (mise, podman, GH CLI) are installed and configured.