Skip to content

Unify agent docs: merge CLAUDE.md into AGENTS.md, symlink the rest#425

Merged
0xLeif merged 1 commit into
mainfrom
chore/unify-agent-docs
Jun 23, 2026
Merged

Unify agent docs: merge CLAUDE.md into AGENTS.md, symlink the rest#425
0xLeif merged 1 commit into
mainfrom
chore/unify-agent-docs

Conversation

@0xLeif

@0xLeif 0xLeif commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Summary

CLAUDE.md and AGENTS.md were two separate, non-overlapping docs that both had to be hand-maintained:

  • CLAUDE.md — codebase map (src/ module layout), build/test commands, repo conventions
  • AGENTS.md — the agent command/usage tour (--json surface, workflows, AI providers)

This folds CLAUDE.md's unique content into AGENTS.md under a new "Working on fledge's own codebase" section, then replaces CLAUDE.md with a symlink → AGENTS.md. One source of truth; AGENTS.md is the emerging cross-tool standard name and Claude Code resolves the symlink transparently.

Refreshed while merging:

Caveat — Windows symlinks

git stores CLAUDE.md as a symlink (mode 120000). Windows clones need core.symlinks=true (+ Developer Mode) to materialize it as a real link rather than a 1-line text file containing AGENTS.md. macOS/Linux are unaffected. Flagging since this repo has windows-latest CI and Windows users.

Test Plan

  • CLAUDE.md resolves to merged AGENTS.md content (verified head/grep through the link)
  • git records CLAUDE.md as symlink (mode 120000), not a regular blob
  • No code change; src/ untouched

🤖 Generated with Claude Code

…the rest

CLAUDE.md (codebase map, build/test, conventions) and AGENTS.md (command/usage
tour) were two separate, non-overlapping docs that both had to be kept in sync
by hand. Fold CLAUDE.md's unique content into AGENTS.md as a new "Working on
fledge's own codebase" section, then replace CLAUDE.md with a symlink → AGENTS.md
so there's a single source of truth. AGENTS.md is the cross-tool standard name;
Claude Code resolves the symlink transparently.

Refreshed while merging: `src/spec/` now lists `engine`; the spec-check
convention notes the new specsync delegation; dropped the stale `Formula/` line.

Note: git stores CLAUDE.md as a symlink (mode 120000). Windows clones need
core.symlinks=true (+ Developer Mode) to materialize it as a link rather than a
text file; macOS/Linux are unaffected.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@0xLeif 0xLeif requested a review from a team as a code owner June 23, 2026 23:41
@0xLeif 0xLeif requested review from 0xGaspar, Kyntrin and tofu-ux June 23, 2026 23:41

@gemini-code-assist gemini-code-assist 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.

Code Review

This pull request restructures the project's documentation by moving the development guidelines, build/test instructions, and architecture source map from the main README (which was deleted) into AGENTS.md, and introduces a CLAUDE.md file. The review feedback correctly points out that development commands, such as running lanes or checking specs, should be executed using the local development version via cargo run -- instead of the globally installed fledge binary to ensure local changes are tested.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread AGENTS.md
cargo fmt --check
```

Or via fledge's own lanes: `fledge lanes run pre-commit` (fmt + lint + test + spec-check).

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

When working on fledge's own codebase, running the globally installed fledge binary will not use your local changes to the CLI or runner. It is safer to run the local development version using cargo run --.

Suggested change:

Or via fledge's own lanes: `cargo run -- lanes run pre-commit` (fmt + lint + test + spec-check).

Comment thread AGENTS.md
### Conventions

- Specs are the source of truth — read before modifying code
- Run `fledge spec check` before committing. It delegates to the `specsync` binary when installed (matching CI's export-coverage validation) and falls back to a structural check otherwise

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

Using the globally installed fledge binary to run spec check will execute the installed version rather than your local changes. When modifying fledge itself, you should run the local development version via cargo run --.

Suggested change:

- Run `cargo run -- spec check` before committing. It delegates to the `specsync` binary when installed (matching CI's export-coverage validation) and falls back to a structural check otherwise

@0xLeif 0xLeif merged commit 14cec6e into main Jun 23, 2026
3 checks passed
@0xLeif 0xLeif deleted the chore/unify-agent-docs branch June 23, 2026 23:43
@0xLeif 0xLeif mentioned this pull request Jun 23, 2026
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.

1 participant