repo-setup

Configures a repository for autonomous TDD development through interactive setup.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/petemcw/farseer --skill repo-setup-petemcw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-setup
Source: https://github.com/petemcw/farseer/tree/main/skills/repo-setup
Command: npx skills add https://github.com/petemcw/farseer --skill repo-setup-petemcw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a repository for autonomous, TDD-based development requires creating consistent configuration files for testing, linting, architecture, domain vocabulary, and issue tracking. Doing this manually is error-prone and often leaves gaps that break downstream automation. ## Core Features & Use Cases - Auto-Detection of Tech Stack: Scans composer.json, package.json, Cargo.toml, go.mod, and other manifest files to detect language, framework, test runner, and linter. - Interactive Configuration: Asks structured questions about test commands, parallel execution, architectural patterns, coverage requirements, and issue tracker choice (GitHub via gh CLI or local Markdown). - Config File Generation: Creates .farseer/ config files (testing.md, code-standards.md, architecture.md, domain.md, issue-tracker.md, issue-labels.md) plus an Agent Skills block in CLAUDE.md or AGENTS.md. - Use Case: After cloning a Laravel project, run the setup once to detect Pest and Pint, record an 80% coverage requirement, choose GitHub Issues as the tracker, and scaffold all configuration so planning and orchestration skills work immediately. ## Quick Start Ask the assistant to set up this repository for Farseer autonomous development and answer the interactive configuration questions.

Frequently Asked Questions about repo-setup

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

FAQPage Schema
How do I set up a repository for autonomous development with Farseer?▼

Run the repo-setup skill once per project. It auto-detects your stack from manifest files, asks about test commands, coverage, and issue tracker, then creates all configuration files in .farseer/ plus a CLAUDE.md or AGENTS.md.

What files does Farseer repo setup create?▼

It creates .farseer/testing.md, code-standards.md, architecture.md, domain.md, issue-tracker.md, and issue-labels.md, and adds an Agent Skills block to CLAUDE.md or AGENTS.md in the project root.

Does repo setup support GitHub Issues and local Markdown trackers?▼

Yes. GitHub Issues uses the gh CLI with native blocked-by relationships, while local Markdown stores issues as files under .farseer/plans/{plan-name}/issues/. Other trackers can be recorded as freeform prose.

Will repo setup overwrite my existing CLAUDE.md or config files?▼

No. The skill checks for existing configuration first, edits the existing CLAUDE.md or AGENTS.md in place, and never overwrites files without explicit confirmation. If fully configured, it tells you to delete .farseer/ before rerunning.

Which technology stacks can repo setup auto-detect?▼

It detects PHP/Laravel/Symfony via composer.json, Node.js/React/Vue via package.json, Rust via Cargo.toml, Go via go.mod, Python via pyproject.toml, Ruby via Gemfile, Java via pom.xml, and .NET via csproj files.