setup-initial-repo

Bootstrap a new repository from SPEC.md with agent instructions, command targets, git identity, and remote.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/byron1st/personal-harness --skill setup-initial-repo-byron1st
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup-initial-repo
Source: https://github.com/byron1st/personal-harness/tree/main/skills/setup-initial-repo
Command: npx skills add https://github.com/byron1st/personal-harness --skill setup-initial-repo-byron1st

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up a new project repository involves many repetitive, error-prone steps: writing agent instruction files, wiring Makefile or package.json commands, configuring git identity, creating remotes, and building .gitignore. This Skill automates that entire bootstrap from a single SPEC.md so a developer and an AI coding agent can start working immediately. ## Core Features & Use Cases - SPEC-driven scaffolding: Reads docs/SPEC.md or SPEC.md, detects the project type (Go, Swift/macOS, TypeScript/Next.js), and generates a matching command surface (Makefile targets or package.json scripts) plus a tailored .gitignore. - Agent file generation: Creates CLAUDE.md or AGENTS.md (never both) following a strict section template, with every quoted command backed by a real Makefile target or package.json script, English-only and under 150 lines. - Git identity and remote setup: Applies local (never global) git user.email/user.name after explicit confirmation, wires an existing origin URL, or creates a private GitHub repo via gh for personal projects only. - Swift project skills: For Swift/macOS projects, copies a fixed set of SwiftUI/macOS Agent Skills into .agents/skills via a script so they travel with the repository. - Use Case: You just wrote a SPEC.md for a new Go backend. Run this Skill to get an initialized git repo, a Makefile with test/lint/coverage/mutation targets, an AGENTS.md referencing those targets, a .gitignore, and a private GitHub remote — all confirmed step by step before any irreversible action. ## Quick Start Ask the agent to run the setup-initial-repo skill to bootstrap this project from my SPEC.md, choosing AGENTS.md and a personal git identity.

Frequently Asked Questions about setup-initial-repo

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

FAQPage Schema
How do I bootstrap a new repository from a SPEC.md file?▼

Place your spec at docs/SPEC.md or SPEC.md in the project root, then run this Skill. It reads the Tech Stack section, detects the project type, and generates the agent file, command surface, .gitignore, git identity, and remote in sequence with confirmations before irreversible steps.

Should I use CLAUDE.md or AGENTS.md for my project?▼

Pick exactly one to avoid instruction drift. Use CLAUDE.md when Claude Code is the primary agent; use AGENTS.md for Grok Build, Codex, or Cursor. If both already exist, the Skill asks which to keep and recommends deleting the other.

Which project types does the command surface generation support?▼

Go projects get a Makefile with format, lint, check, test, race, coverage, mutation testing, and gen targets. Swift/macOS projects get a SwiftFormat/SwiftLint Makefile, and TypeScript/Next.js projects get package.json scripts using ESLint, Vitest, Playwright, and Stryker.

Can this Skill create a GitHub remote automatically?▼

Yes, but only for personal repositories, using `gh repo create <owner>/<name> --private --source=. --remote=origin`. For work repositories it never auto-creates a remote; you must create the repo through your organization's process and provide the URL.

Does the Skill push commits or change global git config?▼

No. Git identity is always set locally per repository, never with --global. The Skill makes the initial commit only after your confirmation and never runs git push; you push manually after reviewing the commit.

What happens if my project has no SPEC.md yet?▼

The Skill stops and asks where the spec lives or suggests running a spec-creation step first. It does not invent a SPEC.md, because the Tech Stack section drives language detection and all downstream scaffolding decisions.