t1281: Deduplicate shared rules across context chain (pass 1)#2039
t1281: Deduplicate shared rules across context chain (pass 1)#2039marcusquinn merged 5 commits intomainfrom
Conversation
Keep build.txt as authoritative source. Replace .agents/AGENTS.md verbose pre-edit section (24 lines) with pointer + unique subagent restrictions only. Replace build-plus.md references with one-liners pointing to build.txt.
build.txt "Completion and quality discipline" section is authoritative (20 lines). Remove duplicate 10-line block from .agents/AGENTS.md and 8-line block from repo AGENTS.md, replacing with one-line pointers.
…ng dirs (t1281) (c) File discovery: replace 13-line table in .agents/AGENTS.md with pointer. (d) Security: keep only unique config templates line, replace rest with pointer. (e) Working directories: keep only agent tiers detail, replace tree with pointer. (f-partial) Critical Rules: replace 10-line block with single pointer line.
…epo AGENTS.md (t1281) (f) Quality standards: replace inline list in repo AGENTS.md with pointer to build.txt. (g) Development lifecycle: replace 16-line block in repo AGENTS.md with pointer to .agents/AGENTS.md (which has the more complete version). (d-repo) Security: replace 5-line block with pointer, keep unique contributor rule.
…ule (t1281) Replace bot reviewer feedback paragraph with pointer to build.txt AI Suggestion Verification section. Replace compaction survival rule with pointer. Saves ~370 additional bytes.
Summary of ChangesHello @marcusquinn, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refactors how shared operational rules are managed across various agent configuration files. By centralizing common guidelines in Highlights
Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
WalkthroughThis PR consolidates agent documentation by replacing detailed, explicit operational rules with concise references to centralized prompt documentation ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report �[0;34m[INFO]�[0m Latest Quality Status: �[0;34m[INFO]�[0m Recent monitoring activity: 📈 Current Quality Metrics
Generated on: Sat Feb 21 00:25:37 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
The pull request effectively deduplicates shared rules across the context chain, leading to significant token savings (~1,068 tokens per session). This is a great optimization for LLM-based workflows. The unique content in each file has been preserved while common rules are now centralized in prompts/build.txt. My main feedback is regarding the loss of markdown formatting (backticks) for file paths and script names in the newly added pointer lines, which affects readability and consistency with the existing documentation style.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.agents/build-plus.md (1)
103-103:pre-edit-check.shshould use its full path for consistency.Every other script reference in this file uses an absolute path (e.g.,
~/.aidevops/agents/scripts/memory-helper.sh,~/.aidevops/agents/scripts/planning-commit-helper.sh). The barepre-edit-check.shsilently assumes~/.aidevops/agents/scripts/is on$PATH, which isn't documented anywhere and diverges from the established pattern in.agents/AGENTS.md's Quick Reference (~/.aidevops/agents/scripts/[service]-helper.sh).♻️ Suggested consistent form
-1. Pre-edit check: run `pre-edit-check.sh` before any edit (see `prompts/build.txt`) +1. Pre-edit check: run `~/.aidevops/agents/scripts/pre-edit-check.sh` before any edit (see `prompts/build.txt`)Apply the same fix at Line 315.
Also applies to: 315-315
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.agents/build-plus.md at line 103, Replace the bare script reference pre-edit-check.sh with the full path used elsewhere (~/.aidevops/agents/scripts/pre-edit-check.sh) to match the established pattern; update both occurrences (the one shown and the other at the same spot referenced around line 315) so all script references in .agents/build-plus.md consistently use the absolute ~/.aidevops/agents/scripts/ path.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.agents/build-plus.md:
- Line 103: Replace the bare script reference pre-edit-check.sh with the full
path used elsewhere (~/.aidevops/agents/scripts/pre-edit-check.sh) to match the
established pattern; update both occurrences (the one shown and the other at the
same spot referenced around line 315) so all script references in
.agents/build-plus.md consistently use the absolute ~/.aidevops/agents/scripts/
path.
1 participant
Summary
Changes by deduplication target
File size results
Verification
Ref #2036
Summary by CodeRabbit