CLAUDE.md Generator — GitHub Action for auto-generating governance files

[goblinmode2700]

Hey everyone! Built a GitHub Action that auto-generates CLAUDE.md files by analyzing your repo's actual structure.

The Problem

Writing a good CLAUDE.md from scratch is tedious. Most of us either skip it or write a minimal one — which means Claude Code doesn't understand our project's conventions as well as it could.

The Solution

A GitHub Action that scans your repo and generates a proper CLAUDE.md with:

• Stack detection — 20+ frameworks (Next.js, FastAPI, Django, Rails, Go, Rust, etc.)
• Tool detection — linters, formatters, databases, deployment targets
• Build commands — auto-discovers test/build/lint commands from config files
• Monorepo support — Turborepo, Nx, Lerna
• 3 styles — minimal, standard, comprehensive

Pure bash, no API keys, no tokens.

Quick Start

# .github/workflows/generate-claude-md.yml
name: Generate CLAUDE.md
on:
  push:
    branches: [main]
  workflow_dispatch:

jobs:
  generate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: goblinmode2700/claude-md-generator@v1
        with:
          style: standard

Repo: https://github.com/goblinmode2700/claude-md-generator

Would love feedback on what frameworks or conventions to add detection for!

[affaan-m]

Auto-generating CLAUDE.md from actual repo structure is a useful idea, especially if it discovers real commands instead of inventing conventions.

The safety boundary I would keep is: generate a PR or draft file, never overwrite the maintainer file silently. A good generated CLAUDE.md should include confidence markers for detected commands/frameworks and leave unknown project policy blank instead of guessing.

For ECC-style projects, I would also consider AGENTS.md output or a split model:

• short always-on project rules
• detected commands/test gates
• optional deeper workflow notes

That keeps the generated file useful without turning it into a huge prompt dump.