agentleFS
Sign inStart free
martincjarvismartincjarvis/development-skills/skills/repository-foundation-bootstrap/SKILL.md

repository-foundation-bootstrap

Skill4 starsChanged 10 months agoMITView on GitHub

Use this skill when bootstrapping a new repository or migrating an existing repo to conform to this skill library's standards, ensuring a clean, minimal foundation before feature work begins.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Plan: Use brainstorming and writing-plans to define the bootstrap sequence and rollback approach.

    line 46
  2. Very specific:

    Verification: Run required verification (including security checks when applicable) and ensure zero warnings (see quality-gate-enforcement).

    line 53
  3. Distinctive:

    If safety or correctness conflicts arise, P0/P1 skills override this skill.

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Repository Foundation Bootstrap

Intent

Establish a clean, standards-aligned repository foundation that supports both new (greenfield) and existing (brownfield) codebases without introducing drift or bypassing quality gates.

When to Use

  • Starting a new repository from scratch.
  • Migrating a brownfield repository to this library's standards.
  • Rebuilding or re-establishing repo structure, tooling, or governance.

Precondition Failure Signal

  • Repository lacks a verified baseline structure or consistent tooling.
  • Quality gates or tooling are introduced on top of unresolved warnings.
  • Brownfield migration starts without impact analysis or a transition plan.

Postcondition Success Signal

  • Repository baseline is documented and verified with zero warnings.
  • Greenfield or brownfield path is explicit and approved.
  • Tooling and governance alignment is reproducible and reviewable.

Process

  1. Source Review: Inspect current repo state (or confirm greenfield) and identify missing baseline elements.
  2. Scope Decision: Declare greenfield vs brownfield path and apply incremental-change-impact for brownfield migrations.
  3. Plan: Use brainstorming and writing-plans to define the bootstrap sequence and rollback approach.
  4. Implementation:
    • Greenfield: initialize repo structure, commit baseline scaffolding, and align configuration with repository standards.
    • Brownfield: apply changes incrementally using safe-brownfield-refactor and best-practice-introduction.
  5. Verification: Run required verification (including security checks when applicable) and ensure zero warnings (see quality-gate-enforcement).
  6. Documentation: Record decisions in ADRs when structure or tooling changes are introduced.
  7. Review: Tech Lead and Platform/DevOps review baseline integrity, migration safety, and CI/CD alignment.

Example Test / Validation

  • Baseline verification suite passes with zero warnings after bootstrap.

Common Red Flags / Guardrail Violations

  • Enabling gates before resolving baseline warnings.
  • Migrating brownfield repos without impact analysis or rollback plan.
  • Applying broad changes without ADRs for structure/tooling decisions.

Recommended Review Personas

  • Tech Lead - validates scope, sequencing, and architectural intent.
  • Platform/DevOps Engineer - validates tooling alignment and CI/CD impact.

Skill Priority

P2 - Consistency & Governance

Conflict Resolution Rules

  • If safety or correctness conflicts arise, P0/P1 skills override this skill.
  • Brownfield migrations must defer to safe-brownfield-refactor and incremental-change-impact sequencing.

Conceptual Dependencies

  • brainstorming
  • writing-plans
  • incremental-change-impact
  • safe-brownfield-refactor
  • best-practice-introduction
  • quality-gate-enforcement
  • ci-cd-conformance
  • static-analysis-security (when security posture changes)

Classification

Governance Core

Notes

This skill defines the repository foundation. It does not replace greenfield-baseline for component-level setup; use both when needed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free