Skip to content

docs(agents): add a GEMINI.md pointer to the maintained instructions - #91

Open
hyperpolymath wants to merge 1 commit into
mainfrom
chore/llm-pointer-2026-09-08
Open

docs(agents): add a GEMINI.md pointer to the maintained instructions#91
hyperpolymath wants to merge 1 commit into
mainfrom
chore/llm-pointer-2026-09-08

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Adds a GEMINI.md pointer file to this repository.

Why. An estate-wide census found a large asymmetry in agent-instruction
files: CLAUDE.md was present almost everywhere, GEMINI.md in a handful of
repositories. Any coding agent that looks for GEMINI.md and does not find one
proceeds with no repository-specific instructions at all.

This file is a pointer, not a second copy of the instructions. Duplicating
guidance across per-agent files guarantees the copies drift. The pointer
redirects to whichever file this repository actually maintains — AGENTS.md
where one exists, otherwise CLAUDE.md — and says to retarget it at
AGENTS.md when one lands.

How this commit was built. The change was made with git plumbing against
origin/<default branch>, not by staging a working tree. The branch contains
exactly one commit adding exactly one file, and carries none of the unrelated
local state present in this checkout. A per-repository assertion required
git diff --name-only <base> <commit> to equal the expected path set exactly,
or the branch was never created.

This PR is opened as a draft on purpose. It is part of a bulk campaign and
is not requesting a merge. Review and merge at your discretion.

🤖 Generated with Claude Code

https://claude.ai/code/session_011eQ7hibx92N7fBDtwgReWk

Adds a GEMINI.md pointer so Gemini-family agents are not blind to the
repository instructions that CLAUDE.md or AGENTS.md already carries
(task #50). The file is a pointer, never a duplicate of the rules.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011eQ7hibx92N7fBDtwgReWk
@coderabbitai

coderabbitaiBot commented Sep 8, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 79c64663-8312-456b-bc9f-bfeebc950077

📥 Commits

Reviewing files that changed from the base of the PR and between 5e069b9 and c59300b.

📒 Files selected for processing (1)
  • GEMINI.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (7)
  • GitHub Check: CodeQL
  • GitHub Check: Dogfooding compliance summary
  • GitHub Check: governance / Validate Hypatia Baseline
  • GitHub Check: governance / Workflow security linter
  • GitHub Check: governance / Trusted-base reduction policy
  • GitHub Check: scan / Hypatia Neurosymbolic Analysis
  • GitHub Check: analyze (actions, none)
⚠️ CI failures not shown inline (2)

GitHub Actions: Central Estate CI/CD Audit / 0_estate-audit.txt: docs(agents): add a GEMINI.md pointer to the maintained instructions

Conclusion: failure

View job details

##[group]Run # Presence-only checking rewards filler. This gate previously demanded
�[36;1m# Presence-only checking rewards filler. This gate previously demanded�[0m
�[36;1m# ARCHITECTURE.md / MAINTAINERS.adoc / GOVERNANCE.md and checked only�[0m
�[36;1m# that the paths existed — so the cheapest way to pass was to commit�[0m
�[36;1m# template boilerplate. That happened: an estate repo acquired an�[0m
�[36;1m# ARCHITECTURE.md describing a directory layout it does not have, a�[0m
�[36;1m# MAINTAINERS naming a different account as owner, and a mise.toml�[0m
�[36;1m# pinning `zig = "latest"` against that repo's own .tool-versions.�[0m
�[36;1m# All three would have passed. So: presence, THEN format, THEN substance.�[0m
�[36;1m#�[0m
�[36;1m# Format policy (estate):�[0m
�[36;1m# .adoc documentation (default)�[0m
�[36;1m# .md wiki content only — plus a transitional allowance for the�[0m
�[36;1m# GitHub-mandated files, which are migrating to berrywiki format�[0m
�[36;1m# .txt licence texts�[0m
�[36;1m# fixed names GitHub or convention dictates (CODEOWNERS, funding.yml,�[0m
�[36;1m# NOTICE, AUTHORS, MAINTAINERS) keep their form�[0m
�[36;1mset -uo pipefail�[0m
�[36;1mfail=0�[0m
�[36;1m�[0m
�[36;1m# --- presence, accepting every policy-legal form -------------------�[0m
�[36;1m# "name:form1,form2,..." — first existing form wins.�[0m
�[36;1mdeclare -a required=(�[0m
�[36;1m ".editorconfig:.editorconfig"�[0m
�[36;1m ".gitignore:.gitignore"�[0m
�[36;1m ".gitattributes:.gitattributes"�[0m
�[36;1m "CODEOWNERS:CODEOWNERS,.github/CODEOWNERS,docs/CODEOWNERS"�[0m
�[36;1m "GOVERNANCE:GOVERNANCE.adoc,GOVERNANCE.md"�[0m
�[36;1m "ARCHITECTURE:ARCHITECTURE.adoc,ARCHITECTURE.md,docs/architecture/README.adoc,TOPOLOGY.adoc,TOPOLOGY.md"�[0m
�[36;1m "MAINTAINERS:MAINTAINERS,MAINTAINERS.adoc,MAINTAINERS.md"�[0m
�[36;1m "toolchain:.tool-versions,mise.toml"�[0m
�[36;1m)�[0m
�[36;1m�[0m
�[36;1mdeclare -A found=()�[0m
�[36;1...

GitHub Actions: Central Estate CI/CD Audit / estate-audit: docs(agents): add a GEMINI.md pointer to the maintained instructions

Conclusion: failure

View job details

##[group]Run # Presence-only checking rewards filler. This gate previously demanded
�[36;1m# Presence-only checking rewards filler. This gate previously demanded�[0m
�[36;1m# ARCHITECTURE.md / MAINTAINERS.adoc / GOVERNANCE.md and checked only�[0m
�[36;1m# that the paths existed — so the cheapest way to pass was to commit�[0m
�[36;1m# template boilerplate. That happened: an estate repo acquired an�[0m
�[36;1m# ARCHITECTURE.md describing a directory layout it does not have, a�[0m
�[36;1m# MAINTAINERS naming a different account as owner, and a mise.toml�[0m
�[36;1m# pinning `zig = "latest"` against that repo's own .tool-versions.�[0m
�[36;1m# All three would have passed. So: presence, THEN format, THEN substance.�[0m
�[36;1m#�[0m
�[36;1m# Format policy (estate):�[0m
�[36;1m# .adoc documentation (default)�[0m
�[36;1m# .md wiki content only — plus a transitional allowance for the�[0m
�[36;1m# GitHub-mandated files, which are migrating to berrywiki format�[0m
�[36;1m# .txt licence texts�[0m
�[36;1m# fixed names GitHub or convention dictates (CODEOWNERS, funding.yml,�[0m
�[36;1m# NOTICE, AUTHORS, MAINTAINERS) keep their form�[0m
�[36;1mset -uo pipefail�[0m
�[36;1mfail=0�[0m
�[36;1m�[0m
�[36;1m# --- presence, accepting every policy-legal form -------------------�[0m
�[36;1m# "name:form1,form2,..." — first existing form wins.�[0m
�[36;1mdeclare -a required=(�[0m
�[36;1m ".editorconfig:.editorconfig"�[0m
�[36;1m ".gitignore:.gitignore"�[0m
�[36;1m ".gitattributes:.gitattributes"�[0m
�[36;1m "CODEOWNERS:CODEOWNERS,.github/CODEOWNERS,docs/CODEOWNERS"�[0m
�[36;1m "GOVERNANCE:GOVERNANCE.adoc,GOVERNANCE.md"�[0m
�[36;1m "ARCHITECTURE:ARCHITECTURE.adoc,ARCHITECTURE.md,docs/architecture/README.adoc,TOPOLOGY.adoc,TOPOLOGY.md"�[0m
�[36;1m "MAINTAINERS:MAINTAINERS,MAINTAINERS.adoc,MAINTAINERS.md"�[0m
�[36;1m "toolchain:.tool-versions,mise.toml"�[0m
�[36;1m)�[0m
�[36;1m�[0m
�[36;1mdeclare -A found=()�[0m
�[36;1...
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: hyperpolymath/anamnesis
Timestamp: 2026-09-08T23:48:24.702Z
Learning: Do not duplicate rules here.
🪛 GitHub Check: Hypatia
GEMINI.md

[warning] 1-1: Hypatia root_hygiene: stale
Stale AI session file -- delete

🔇 Additional comments (1)
GEMINI.md (1)

1-8: LGTM!


📝 Summary

Summary by CodeRabbit

  • Documentation

    • Added guidance for development assistants to follow the project’s established contribution rules.
    • Clarified how future shared guidance should be incorporated without duplicating existing instructions.
  • User Impact

    • No changes to application functionality or the end-user experience.

Walkthrough

Added GEMINI.md with guidance for coding agents. It points agents to CLAUDE.md until AGENTS.md exists and excludes Claude Code-specific instructions.

Changes

Agent guidance

Layer / File(s)Summary
Agent instruction pointer
GEMINI.md
The new guidance points agents to CLAUDE.md, avoids duplicated rules, excludes Claude Code-specific content, and directs future updates to AGENTS.md.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk:⚪ Minimal · up to c5930

This adds a pointer for Gemini-family coding agents to the repository guidance without changing runtime behavior or product data. No merge-readiness risk remains.

Suggested reviewers:metadatastician

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check nameStatusExplanation
Docstring Coverage✅ PassedNo functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check✅ PassedCheck skipped because no linked issues were found for this pull request.
Out of Scope Changes check✅ PassedCheck skipped because no linked issues were found for this pull request.
Title check✅ PassedThe title clearly and concisely describes the main change: adding a GEMINI.md pointer to the maintained agent instructions.
Description check✅ PassedThe description directly explains the GEMINI.md pointer, its purpose, redirect behaviour, and relationship to the changeset.
✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch

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

A rabbit reads the guidance clear
One pointer keeps the rules near
No copied words hop through the gate
AGENTS.md will change the state
The burrow stays tidy and great

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

@sonarqubecloud

Copy link
Copy Markdown

Comment threadGEMINI.md
@@ -0,0 +1,8 @@
# Pointer
@hyperpolymath
hyperpolymath marked this pull request as ready for review September 8, 2026 23:59
@hyperpolymath
hyperpolymath enabled auto-merge (squash) September 9, 2026 00:00
Sign up for freeto 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

@hyperpolymath@github-advanced-security