repo-bootstrap

Bootstrap new repositories with an interview-first workflow and standardized topology.

Updated Jan 20, 2026

Search Tags:#automation #verification #bootstrap #repository-setup #tooling-baseline #capability-first

Ready to run

npx skills add https://github.com/jmmarotta/skills --skill repo-bootstrap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-bootstrap
Source: https://github.com/jmmarotta/skills/tree/main/skills/repo-bootstrap
Command: npx skills add https://github.com/jmmarotta/skills --skill repo-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often bootstrap new repositories with inconsistent scaffolds, tooling, and verification plans, leading to misalignment and friction.

Core Features & Use Cases

Structured interview-driven setup guiding language profile, topology, and dependencies.
Capability-first repository organization with co-located code, docs, and tests.
Automated baseline tooling including hooks, dependency management, and CI configuration, plus a formal verification plan.

Quick Start

Run the repository bootstrap workflow to scaffold a new project with the recommended layout, tooling, and verification plan.

Frequently Asked Questions about repo-bootstrap

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

FAQPage Schema

How do I bootstrap a new repository with a standardized topology and tooling baseline?▼

Bootstrapping a new repository applies an interview-first workflow to establish a capability-first organization, co-locating code, docs, and tests alongside automated baseline tooling and verification planning.

What is an interview-first workflow for repository setup?▼

An interview-first workflow for repository setup guides language profile selection, topology decisions, and dependency mapping to ensure consistent scaffolding and eliminate team misalignment before generating the project structure.

How do I create a closed-loop verification plan with automated quality gates for a new software project?▼

Creating a closed-loop verification plan involves applying standardized topology during repository setup, which configures automated quality gates and manual checks to ensure comprehensive project validation.

Does repository setup work without pre-configured dependencies or environments?▼

Yes, repository setup works without pre-configured dependencies because the interview-driven workflow establishes the language profile and tooling baseline from scratch to scaffold the initial project environment.

What's the best way to organize a repository for capability-first development?▼

The best way to organize for capability-first development is applying a standardized topology that co-locates code, docs, and tests together, ensuring project structure directly aligns with functional capabilities.

Why does inconsistent repository scaffolding cause friction in software projects?▼

Inconsistent repository scaffolding causes friction because varying tooling baselines and missing verification plans lead to team misalignment, making automated quality gates and manual checks difficult to standardize across projects.