Skip to content

docs: add canonical AGENTS.md + CLAUDE.md shim, re-track agent docs, ignore .claude/.agents#13

Merged
w7-mgfcode merged 3 commits into
mainfrom
docs/restore-claude-md
Jun 27, 2026
Merged

docs: add canonical AGENTS.md + CLAUDE.md shim, re-track agent docs, ignore .claude/.agents#13
w7-mgfcode merged 3 commits into
mainfrom
docs/restore-claude-md

Conversation

@w7-mgfcode

@w7-mgfcode w7-mgfcode commented Jun 27, 2026

Copy link
Copy Markdown
Owner

Summary

Establishes the canonical-source agent-doc model and cleans up assistant-file tracking.

Changes

  • AGENTS.md — now tracked as the single canonical source of agent operating rules (purpose, build/test commands, code style, architecture notes, validation, security, conventions). Repo-verified; unchanged content.
  • CLAUDE.md — reduced from a 64-line duplicate to an 11-line thin shim that @AGENTS.md-imports the canonical rules and adds only Claude-specific runtime notes. No duplicated policy (single source of truth).
  • .gitignoreCLAUDE.md removed from ignore (now tracked); .claude/ and .agents/ ignored as local-only assistant tooling.

Background

CLAUDE.md (and a .claude/ tooling dir) were deleted + gitignored in PR #6. This restores shared agent context in the modern AGENTS.md-canonical + provider-shim layout, while keeping machine-local tooling (.claude/, .agents/) out of git.

Validation

  • maintaining-agent-docs validator: 0 errors, 0 warnings (1 advisory info).
  • git check-ignore: CLAUDE.md/AGENTS.md trackable; .claude/, .agents/ ignored.
  • Branch rebased on latest main; CI ShellCheck + Compose Validate required.

Recreate the root CLAUDE.md (project context for Claude Code) and remove it from
.gitignore so it is committed and shared again; .claude/ stays ignored. The file
captures per-project commands, the four validation gates, and the non-obvious
gotchas surfaced during end-to-end validation (set -e increment footgun,
stderr/stdout JSON discipline, adminer dual-network/loopback, the spamd-is-not-a-
milter trap, php-fpm TCP, init.sql/${MYSQL_DATABASE}, scratch-image healthchecks).
@sourcery-ai

sourcery-ai Bot commented Jun 27, 2026

Copy link
Copy Markdown

Reviewer's Guide

Restores the root CLAUDE.md documentation file to version control and updates .gitignore so that only the .claude/ directory remains ignored, reintroducing a detailed, bilingual project guide for Claude Code while keeping other ignore rules intact.

File-Level Changes

Change Details Files
Restore and re-track the CLAUDE.md documentation file as a comprehensive project guide for Claude Code.
  • Create a new CLAUDE.md at the repository root describing repository layout, per-project responsibilities, and key components.
  • Document common docker compose workflows and validation commands that align with CI checks (ShellCheck, Compose config, and project P02/P03 test suites).
  • Capture non-obvious operational gotchas for each project (shell scripting pitfalls, JSON output discipline, Adminer networking, mail stack behavior, php-fpm/MySQL specifics, CoreDNS limitations).
  • Describe project-wide conventions, including Bash style, bilingual documentation expectations, branch protection rules, and policy on AI attribution in commits/PRs.
CLAUDE.md
Adjust ignore rules so CLAUDE.md is tracked while continuing to ignore the .claude/ directory.
  • Remove the CLAUDE.md entry from .gitignore so that the file is once again versioned.
  • Keep the .claude/ directory ignored to avoid tracking local Claude configuration or workspace files.
.gitignore

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Jun 27, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@w7-mgfcode, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 34 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 31b6ebad-aa51-43e6-9d01-b786386a7fd1

📥 Commits

Reviewing files that changed from the base of the PR and between ddf9a1c and 9544dbf.

📒 Files selected for processing (3)
  • .gitignore
  • AGENTS.md
  • CLAUDE.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/restore-claude-md

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • The hard-coded test counts in the validation section (e.g., # 42 tests, # 43 tests) are likely to drift over time; consider either omitting the exact numbers or deriving them programmatically in the test runners and describing them more generically here.
  • Several details in the Gotchas section (ports, container names, healthcheck behavior, etc.) are tightly coupled to the current compose definitions; it may be worth explicitly noting that CLAUDE.md should be updated alongside any future compose/service changes to avoid this doc becoming misleading.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The hard-coded test counts in the validation section (e.g., `# 42 tests`, `# 43 tests`) are likely to drift over time; consider either omitting the exact numbers or deriving them programmatically in the test runners and describing them more generically here.
- Several details in the Gotchas section (ports, container names, healthcheck behavior, etc.) are tightly coupled to the current compose definitions; it may be worth explicitly noting that CLAUDE.md should be updated alongside any future compose/service changes to avoid this doc becoming misleading.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

…n shim

Track the existing root AGENTS.md as the single source of agent operating rules,
and replace CLAUDE.md's duplicated policy with a thin shim that imports it
(@AGENTS.md) plus Claude-specific runtime notes. Resolves the single-source-of-
truth drift flagged by the maintaining-agent-docs validator (now 0 warnings).
@w7-mgfcode w7-mgfcode changed the title docs: restore CLAUDE.md and re-track it docs: add canonical AGENTS.md + CLAUDE.md shim, re-track agent docs, ignore .claude/.agents Jun 27, 2026
@w7-mgfcode w7-mgfcode merged commit 889d457 into main Jun 27, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants