chore: untrack gitnexus-generated agent files - #43
Conversation
These files are generated by `gitnexus analyze` as a side effect of indexing this repository. They are development-loop private tooling rather than product, contain no secrets, and are removed going forward. History is deliberately NOT rewritten, so the content remains in past commits. Refs #3177
Security audit — PASSScope audited: this PR's full diff at the head SHA in the table below (independent re-measurement, not a rubber stamp of the commit message). Diff shape: every hunk is a deletion of
Content classification (the load-bearing question): every removed line is generated tool documentation — GitNexus MCP tool usage instructions, generic workflow examples ( Identity: commit author/committer is History: branch is a pure fast-forward of No findings. PASS. |
MichaelTaylor3d
left a comment
There was a problem hiding this comment.
loop-reviewer verdict: PASS
Independent correctness review of the mechanical gitnexus-untrack change (DIG-Network/dig_ecosystem#3177).
Checks performed:
- File count: exactly 9 files changed (6
.claude/skills/gitnexus/**/SKILL.md,.gitignore,AGENTS.md,CLAUDE.md) — confirmed viagh pr diff --name-only. - Deletion justified: fetched
AGENTS.mdandCLAUDE.mdas they exist atorigin/mainand verified programmatically (line-range check against the<!-- gitnexus:start -->/<!-- gitnexus:end -->markers) that zero non-blank lines exist outside the marker block in either file. The deletion loses no authored content because there was none. .gitignore: block is syntactically valid, correctly anchored with leading/(repo root only), appended with a proper preceding blank line (no glue-onto-previous-line defect — this repo's prior.gitignorein the coinstore/DataLayer-Driver cases lacked a trailing newline and the fix correctly inserted one before appending)./CLAUDE.mdis present in the ignore block, consistent with this repo being in the DELETE group (CLAUDE.md here is 100% generated).- Shadow-ignore check: diffed the new ignore patterns against
git ls-tree -r origin/main— no tracked file other than the ones this same PR removes matches the new patterns. - History:
compare/main...<head>reportsaheadwithbehind_by: 0— ordinary fast-forward descendant ofmain, no rewrite. - Commit message / PR title: conventional-commit shaped (
chore(...): ...orchore: ...), explains the "why" (generated, no secrets, history not rewritten).
No blocking findings. No inline threads opened.
Out of scope per brief, not evaluated here: contents of the deleted SKILL.md files (separate security gate).
The ignore comment named a private repository and an internal issue number in a public file, which is the same disclosure class this change set exists to remove; the reference is dropped and the guidance kept.
MichaelTaylor3d
left a comment
There was a problem hiding this comment.
Verdict: PASS
Re-gate at the final head (this repo's DELETE-group PR, follow-up commit applied):
- Follow-up commit
chore: drop private-repo reference from gitignore commentis the sole new commit after the previously-reviewed head; base is still an ancestor (compare API:ahead,behind=0) — no rebase/force-push/amend. - Follow-up diff touches exactly one file (
.gitignore), one line changed. - Final
.gitignore:grep -c dig_ecosystem= 0, no#3177reference remains. - Rest of the gitnexus-ignore block intact:
/AGENTS.md,/CLAUDE.md,/.claude/skills/gitnexus/,/.claude/skills/generated/,/.gitnexus/all present (DELETE group keeps/CLAUDE.mdin the block, matching that bothAGENTS.mdandCLAUDE.mdwere 100% generated here and deleted whole). - Cumulative diff vs base: 9 files, matches the table; nothing extraneous.
Known structural constraint: gh pr review --approve fails here ("Can not approve your own pull request" — same identity authored the PR). Posting as `--comment" with the verdict stated explicitly per DIG-Network/dig_ecosystem#3177 review protocol.
|
Security re-gate — PASS Verified at final head:
Verdict on the removed content: PRIVATE-BUT-HARMLESS. No live vulnerability found. |
Summary
Removes the following files, which are 100% generated by
gitnexus analyzeas a side effect of indexing this repository, from tracking:AGENTS.mdCLAUDE.md.claude/skills/gitnexus/**They are development-loop private tooling rather than product, contain no secrets, and are removed going forward.
.gitignoreis updated so they do not get re-tracked (also covers.claude/skills/generated/and.gitnexus/).History is deliberately NOT rewritten — the content remains recoverable in past commits.
Refs #3177