Conversation
CLAUDE.md contained nothing but the generated <!-- gitnexus --> block, which is already present verbatim in AGENTS.md. Tools that read both prefer CLAUDE.md, so the stub was shadowing this repo's actual conventions. Remove it and gitignore the root path so a future `gitnexus analyze` cannot reintroduce it. Also document the post-analyze cleanup step in the gitnexus-cli skill, since analyze writes both files and has no flag to suppress one. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Patel230
force-pushed
the
chore/agents-md-only
branch
from
September 18, 2026 21:23
b1b1a95 to
bf44f50
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
CLAUDE.mdin this repo contained nothing but the generated<!-- gitnexus -->block — and that block is already present verbatim inAGENTS.md(identical bytes, heading demoted#→##). There was nothing unique to merge.Tools that read both files prefer
CLAUDE.md, so the stub was shadowing this repo's actual conventions (build commands, branch policy, ecosystem boundaries) that live only inAGENTS.md.Changes
CLAUDE.md/CLAUDE.mdso a futuregitnexus analyzecannot reintroduce itWhy the gitignore
gitnexus analyzegenerates both context files and exposes no flag to suppress one (--force,--embeddings,--drop-embeddings,--pdg). Without the ignore rule the stub returns on the next index and silently shadowsAGENTS.mdagain.Verification
Created a
CLAUDE.md, confirmedgit check-ignorematches it andgit statusstays clean.🤖 Generated with Claude Code
Also documents the post-analyze cleanup step in the
gitnexus-cliskill, which is the path agents use to runanalyze.