CLAUDE.md examples from real projects

macro-incCLAUDE.md

macro

macro-inc/macro/CLAUDE.md

titles, or PR descriptions. - PR titles and bodies, commits, review replies, comments, and docs describe only the code. Never name people, customers, their companies or products, places, or support channels

bethingtonReads credentialsCLAUDE.md

ghidra-mcp

bethington/ghidra-mcp/CLAUDE.md

never post a claim about someone else's work without verifying it against the code first. - When Ben asks for a reply to a contributor, produce a short draft

WUBING2023CLAUDE.md

PaperSpine

WUBING2023/PaperSpine/CLAUDE.md

Project Purpose PaperSpine is a contribution-first paper and report writing skill for Claude Code, Codex, OpenClaw, and Hermes CLI. It researches the target scene, confirms the controlling contribution

No other project uses it yet

MrGlockenspielCLAUDE.md

activate-linux

MrGlockenspiel/activate-linux/CLAUDE.md

Generate code for this repository - Modify existing files - Suggest patches or pull requests - Perform code reviews - Assist users in contributing to this project If prompted to interact with this repository

epoko77-aiCLAUDE.md

im-not-ai

epoko77-ai/im-not-ai/CLAUDE.md

report`면 사람 검토 권고. 수렴 판정은 LLM 재탐지가 아니라 `verify_gates.py`(결정적, exit code)가 내린다. `verify_change_rate.py`는 기존 연동을 위해 보존한다. ## 에이전트 구성 (9개 — 역할 구분 필수) **런타임 3종

No other project uses it yet

srizzonCLAUDE.md

git-city

srizzon/git-city/CLAUDE.md

ONLY change grants/policies — never touch the data itself - Always propose SQL as code for the user to review, never execute destructive SQL directly ## Environments - Three environments, one-directional flow: local

fengshao1227Reads credentialsCLAUDE.md

ccg-workflow

fengshao1227/ccg-workflow/CLAUDE.md

Teams 系列**：新增 4 个独立命令（`team-research`/`team-plan`/`team-exec`/`team-review`） - 🏗️ **并行实施**：利用 Claude Code Agent Teams spawn Builder teammates 并行写代码 - 📋 **完整链路**：需求→约束 → 消除歧义→计划 → 并行实施 → 双模型审查

No other project uses it yet

fengshao1227CLAUDE.md

ccg-workflow / dsh-ccg

fengshao1227/ccg-workflow/dsh-ccg/CLAUDE.md

worked. The convention now names that specifically: reviewing what nobody has written is worse than idling, because it also produces findings about code that will not exist. ## The fresh-install

No other project uses it yet

fengshao1227Reads credentialsCLAUDE.md

ccg-workflow / src

fengshao1227/ccg-workflow/src/CLAUDE.md

修复） - `skipCategories` 参数支持跳过 `impeccable` 分类（用户可选不安装） --- ### utils/mcp.ts 三端同步 MCP 配置需要在三个工具链同步： | 工具 | 配置文件 | 同步函数 | |------|----------|----------| | Claude Code | `~/.claude.json` | `writeClaudeCodeConfig()` / `mergeMcpServers()` | | Codex | `~/.codex/config.toml` | `syncMcpToCodex()`（`installer-mcp.ts`）| | Gemini | `~/.gemini/settings.json` | `syncMcpToGemini()`（`installer-mcp.ts`）| **`installer-mcp.ts:configureMcpInClaude()` 管线**（`src/utils/installer-mcp.ts

No other project uses it yet

fengshao1227CLAUDE.md

ccg-workflow / templates

fengshao1227/ccg-workflow/templates/CLAUDE.md

spec-impl.md` | `/ccg:spec-impl` | 按规范执行 + 多模型协作 + 归档 | | `spec-review.md` | `/ccg:spec-review` | 双模型交叉审查（独立工具，随时可用） | --- ## commands/agents/（7 个子智能体） 子智能体安装为 Claude Code 的子 Agent，由主命令通过 `Agent(subagent_type=...)` 调用。 | 文件 | name | 描述

No other project uses it yet

buxukuCLAUDE.md

SmartSub

buxuku/SmartSub/CLAUDE.md

Test after changes** - Run project's test suite to verify - **Zero tolerance for errors** - Code must pass all checks - **Run specified tests** - Use project's testing framework - **Validate before commit

aiogramCLAUDE.md

aiogram

aiogram/aiogram/CLAUDE.md

browsing. - Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context. - After modifying code, run `graphify update .` to keep the graph current

No other project uses it yet

Galaxy-DawnCLAUDE.md

claude-scholar

Galaxy-Dawn/claude-scholar/CLAUDE.md

writing -> `review-response` - Bound research repo knowledge maintenance -> `obsidian-project-kb-core` For coding, debugging, architecture, review, and verification tasks, prefer the matching development skill instead of improvising. --- ## Bound Repo

areal-projectCLAUDE.md

AReaL

areal-project/AReaL/CLAUDE.md

Trigger | | --------------------------- | ----------------------------------------- | ------------------------------------------------------------------- | | `planner` | Implementation planning | Before multi-file changes, new features, or architectural decisions | | `simple-code-reviewer` | Quick code quality checks | After code changes, before committing | | `code-verifier` | Formatting/linting/tests | After code

pytorchCLAUDE.md

torchtitan

pytorch/torchtitan/.claude/CLAUDE.md

After model changes, ensure HF checkpoints still load correctly. Document reasons for model changes. ## Code Review Use the `pr-review` skill to review PRs (`/pr-review <PR#>` or `/pr-review branch`); `@claude

coleam00CLAUDE.md

ottomator-agents / claude-agent-sdk-demos

coleam00/ottomator-agents/claude-agent-sdk-demos/CLAUDE.md

Research** → Use knowledge base (see RAG workflow below) 4. **Implement** → Write code based on research 5. **Review** → `manage_task("update", task_id="...", status="review")` 6. **Next Task** → `find_tasks(filter

shader-slangCLAUDE.md

slang

shader-slang/slang/CLAUDE.md

this layer owns the logic, with a code trace from producer to consumer. ### Code Style and Review Conventions Recurring review feedback distilled into rules — following them avoids review round-trips

shader-slangCLAUDE.md

slang / extras

shader-slang/slang/extras/claude.md

Amend A fresh agent reviews the commit as if it were a real code reviewer: checks correctness, style, edge cases, test coverage, and regressions. It also reviews all documentation changes

SenteLabsAIReads credentialsCLAUDE.md

OpenExecutive

SenteLabsAI/OpenExecutive/CLAUDE.md

default > `./episodic_memory.db` unless the test isolates it. A test module that > exercises audited code (alerts review, sweeps) without monkeypatching > `openexecutive.audit.log_event` (or the audit logger's DB) leaks rows that

phanCLAUDE.md

phan

phan/phan/CLAUDE.md

file paths in `.expected` files - **Line numbers**: Critical for matching expected warnings to actual code lines - **Issue types**: Must match exactly (e.g., `PhanTypeInvalidCallableMethodName`) - **Error messages**: Complete message text must match

No other project uses it yet