ClaudeMD Forge
Generate optimized CLAUDE.md files for AI coding agents in seconds.
Stop hand-rolling CLAUDE.md. Let Forge analyze your codebase and generate a production-grade configuration file that makes Claude Code, Cursor, Windsurf, and Codex actually understand your project.
Why?
AI coding agents are only as good as the context you give them. A well-crafted CLAUDE.md is the difference between an agent that writes idiomatic code and one that fights your conventions on every change.
ClaudeMD Forge:
- Scans your codebase to detect languages, frameworks, and patterns
- Generates a complete CLAUDE.md with coding standards, commands, and anti-patterns
- Audits existing CLAUDE.md files and scores them against best practices
- Framework-aware presets for React, FastAPI, Rust, Django, Next.js, and more
Install
pip install claudemd-forge
Quick Start
# Generate a CLAUDE.md for your project
claudemd-forge generate .
# Audit an existing CLAUDE.md
claudemd-forge audit ./CLAUDE.md
# Interactive setup
claudemd-forge init .
# See what would change
claudemd-forge diff .
# List available presets
claudemd-forge presets
# List framework-specific presets
claudemd-forge frameworks
Example Output
Running claudemd-forge generate . on a FastAPI project produces:
# CLAUDE.md — my-api
## Project Overview
my-api — TODO: Add project description.
## Current State
- **Version**: 0.1.0
- **Language**: Python
- **Files**: 47 across 2 languages
- **Lines**: 3,204
## Tech Stack
- **Language**: Python
- **Framework**: fastapi
- **Package Manager**: pip
- **Linters**: ruff
- **Test Frameworks**: pytest
- **CI/CD**: GitHub Actions
## Coding Standards
- **Naming**: snake_case
- **Type Hints**: present
- **Docstrings**: google style
- **Imports**: absolute
## Common Commands
...
## Anti-Patterns (Do NOT Do)
- Do NOT use synchronous database calls in async endpoints
- Do NOT return raw dicts — use Pydantic response models
- Do NOT use `os.path` — use `pathlib.Path` everywhere
...
GitHub Action
Add automated CLAUDE.md auditing to your CI pipeline:
# .github/workflows/claudemd-audit.yml
name: Audit CLAUDE.md
on: [pull_request]
jobs:
audit:
runs-on: ubuntu-latest
permissions:
pull-requests: write
steps:
- uses: actions/checkout@v6
- uses: Arete-Consortium/claudemd-forge@v0.1.0
with:
fail-below: 40 # Minimum passing score (0-100)
comment: true # Post results as PR comment
The action posts a formatted comment on your PR with score, findings, and recommendations.
Free vs Pro
| Feature | Free | Pro ($8/mo) |
|---|---|---|
generate — scan and produce CLAUDE.md |
Yes | Yes |
audit — score existing CLAUDE.md |
Yes | Yes |
| 11 community presets (FastAPI, React, Rust, Django...) | Yes | Yes |
init — interactive guided setup |
- | Yes |
diff — detect drift between CLAUDE.md and codebase |
- | Yes |
| CI integration — GitHub Action auto-audit on PR | - | Yes |
| 6 premium presets (monorepo, data-science, devops...) | - | Yes |
| Team templates (shared org standards) | - | Planned |
Activate Pro:
export CLAUDEMD_FORGE_LICENSE=CMDF-XXXX-XXXX-XXXX
Framework Presets
| Preset | Description |
|---|---|
python-fastapi |
FastAPI + async patterns |
python-cli |
Python CLI with typer/click |
react-typescript |
React + TypeScript + hooks |
nextjs |
Next.js App Router conventions |
django |
Django with ORM patterns |
rust |
Rust with clippy + proper error handling |
go |
Go with standard project layout |
node-express |
Express.js backend |
Audit Scoring
Forge scores your CLAUDE.md on:
- Section coverage — does it have the essentials?
- Accuracy — does it match your actual codebase?
- Specificity — are instructions actionable or vague?
- Anti-patterns — does it prevent common mistakes?
- Freshness — is it up to date?
Development
# Clone and install
git clone https://github.com/Arete-Consortium/claudemd-forge.git
cd claudemd-forge
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
# Run tests
pytest tests/ -v
# Lint
ruff check src/ tests/
ruff format src/ tests/
License
MIT
Metadata
Release files for claudemd-forge 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| claudemd_forge-0.3.0.tar.gz | 138.0 kB | With provenance | Details for claudemd_forge-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| claudemd_forge-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for claudemd_forge-0.3.0-py3-none-any.whl |
Total release size: 214.8 kB
Release files / claudemd_forge-0.3.0.tar.gz
| Download URL | claudemd_forge-0.3.0.tar.gz |
|---|---|
| Size | 138.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e58f1f7f4fb8c4356bf3eb12421b58b5eaf336fe8eb897f88d41b72ebeaa09b5
|
|
BLAKE2b-256 checksum How to use checksums |
7bb2d3612e7c75a53e019fced233eadcc42f7926f82c2876dfe6770707433c2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 8, 2026.
Transparency logRelease files / claudemd_forge-0.3.0-py3-none-any.whl
| Download URL | claudemd_forge-0.3.0-py3-none-any.whl |
|---|---|
| Size | 76.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9602f20186a3962df6b6424057d0742b7dc9eb4ca2ff5fd919594680dcb542d2
|
|
BLAKE2b-256 checksum How to use checksums |
81ff2cfba4bd5cf7673ba7da5e551ff5856897f2b42e0a876704a60bee482c69
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 8, 2026.
Transparency logSecurity for claudemd-forge 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for claudemd_forge-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.