Auto-generate README and LICENSE files for every GitHub repo

Checks every one of your GitHub repos daily and fills in missing README and LICENSE files with AI.

How the work actually flows

It branches. Exactly one path is taken; runs once per one per repository.

Pattern: Multiple Instances with a priori Run-Time Knowledge (14) · Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig(["daily repository check"]):::trigtime s0["list all repositories"]:::svc s1[["check repo for readme and license"]]:::mi s2["generate missing files"]:::svc s3["commit files to repo"]:::svc trig --> s0 s0 -->|"one per one per repository"| s1 s2 --> s3 gx{"× are files missing"}:::gate s1 --> gx p00["generate readme and license"]:::task gx -->|"files missing"| p00 p10["skip repository"]:::task gx -->|"files present"| p10 jn{"○ "}:::gate p00 --> jn p10 --> jn jn --> s2 out[/"repos have readme and license"/]:::out pay{{"consistent docs with no manual writing"}}:::pay s3 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itAn outside serviceRuns once per itemOne path onlyPaths rejoinResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
SEO & Search OptimizationDevOps & IT Operations
Connects
GitHubGoogle Gemini

The problem it solves

Some of your repositories are missing a README or a license file, and it's easy to forget which ones. Writing decent documentation for every project by hand isn't a priority when you're busy shipping code.

Who it fits

Developers or teams maintaining multiple GitHub repositories.

How it works

  1. On a daily schedule, the workflow lists every repository in your GitHub account
  2. Each repo is checked for an existing README and LICENSE file
  3. If either is missing, AI writes a clean, well-structured README
  4. A standard license file is generated if none exists
  5. The new files are committed directly to the repository
What you get

Repos that always have a README and license

Every GitHub repository automatically gets a clear README and license file, keeping your codebase tidy and complete.

What you get

Repositories with complete, AI-written README files and license files committed automatically.

What you need

A GitHub account and a Google Gemini API key.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook