init-claude-md

Generates a project-level CLAUDE.md from codebase analysis of tech stack, conventions, and commands.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/codewizwit/human-in-the-loop --skill init-claude-md-codewizwit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: init-claude-md
Source: https://github.com/codewizwit/human-in-the-loop/tree/main/lib/skills/init-claude-md
Command: npx skills add https://github.com/codewizwit/human-in-the-loop --skill init-claude-md-codewizwit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Generic CLAUDE.md files produced by default initialization commands contain boilerplate rules that do not reflect how a project actually works. This Skill reads the real codebase first, then writes a project configuration file for Claude Code grounded in evidence from config files, source code, tests, git history, and CI pipelines. ## Core Features & Use Cases - Evidence-based generation: Detects languages, frameworks, test runners, linters, and package managers from manifest files, then reads source and test files to capture real conventions. - Deduplication and enhancement: Skips rules already covered by the user-level ~/.claude/CLAUDE.md or enforced by linters, and can enhance an existing CLAUDE.md instead of replacing it. - Use Case: A developer joins a NestJS monorepo and asks Claude to set up project configuration. The Skill detects pnpm, Jest, co-located tests, and conventional commits, then writes a 60-line CLAUDE.md with only project-specific rules and verified commands. ## Quick Start Ask Claude to generate a CLAUDE.md for this project based on the actual codebase conventions.

Frequently Asked Questions about init-claude-md

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

FAQPage Schema
How do I generate a CLAUDE.md file for my project?▼

Ask Claude to generate or set up a CLAUDE.md, or invoke /init-claude-md directly. The skill analyzes your config files, source code, tests, and git history, then writes a project-specific CLAUDE.md of 30-100 lines.

How is this different from the claude init command?▼

The claude init command produces generic defaults, while this skill reads the actual codebase first. Every rule it writes is traced to evidence found in config files, source patterns, test conventions, or CI configuration.

Can it improve an existing CLAUDE.md without replacing it?▼

Yes, an enhance mode preserves existing content, adds missing sections, updates outdated commands, and flags contradictions between documented rules and actual codebase conventions. You choose enhance, fresh, or review before anything is written.

Does it work with Python, Go, or Rust projects?▼

Yes, it supports multiple ecosystems including JavaScript/TypeScript, Python, Rust, Go, Ruby, Java, and PHP. It detects the stack from manifest files like pyproject.toml, Cargo.toml, go.mod, Gemfile, and pom.xml.

Why does the generated CLAUDE.md skip some obvious rules?▼

Rules already enforced by linters like ESLint or Prettier, or already defined in the user-level ~/.claude/CLAUDE.md, are intentionally omitted to avoid duplication. The file stays focused on project-specific conventions only.