Skip to content

chore: Update AGENTS.md for more efficient use.#515

Merged
kingargyle merged 1 commit intodevelopfrom
dac_AGENTSMD_tweaks
Feb 7, 2026
Merged

chore: Update AGENTS.md for more efficient use.#515
kingargyle merged 1 commit intodevelopfrom
dac_AGENTSMD_tweaks

Conversation

@kingargyle
Copy link
Contributor

@kingargyle kingargyle commented Jan 20, 2026

Breaks up the AGENTS.md for Gemini so that it can better process and keep the context.

Summary by CodeRabbit

  • Documentation
    • Streamlined development guidelines with consolidated core protocols and framework references.
    • Established clear collaboration and communication standards for teams.
    • Defined coding frameworks, architectural patterns, and dependency injection conventions.
    • Added comprehensive testing standards and best practices.

✏️ Tip: You can customize this high-level summary in your review settings.

Breaks up the AGENTS.md for Gemini so that it can better
process and keep the context.
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 20, 2026

Walkthrough

This change refactors agent guidelines documentation from a single comprehensive file into modular, focused reference documents covering communication protocols, constraints, coding frameworks, and testing standards. The original AGENTS.md is streamlined to reference these external documents.

Changes

Cohort / File(s) Summary
Core Agent Documentation Restructure
AGENTS.md
Replaced extensive multi-section guidelines with compact core protocol; introduces references to external constraint documents and simplified Agent Decision Checklist format; removes prior sections on Quick Start, Hard Constraints, Git interaction, Collaboration Protocols, Project Overview, Code Style, and Testing Guidelines.
Agent Guidelines Framework
prompts/agents/COMMUNICATION.md, CONSTRAINTS.md, FRAMEWORKS.md, TESTING.md
Four new documentation files introduced: COMMUNICATION.md establishes collaboration principles and communication templates; CONSTRAINTS.md details hard constraints and Git interaction rules; FRAMEWORKS.md specifies coding standards, DI, MVP, and view binding guidelines; TESTING.md outlines MockK-based testing standards and DI setup in tests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

📚 From mountains of prose, now organized bright,
The docs split asunder, each section just right,
Communication, Constraints, Frameworks in place,
Testing and guidelines all find their own space!
🐰 A burrow well-ordered makes agents run fast!

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore: Update AGENTS.md for more efficient use' is vague and doesn't clearly convey the primary change. While it mentions AGENTS.md, it doesn't explain that the file was restructured into separate constraint and framework documents to improve context processing for AI agents. Consider a more specific title like 'chore: Split AGENTS.md into modular constraint and framework guides' to better communicate the structural reorganization.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

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

@sonarqubecloud
Copy link

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@prompts/agents/CONSTRAINTS.md`:
- Around line 11-19: Update the nested list under the "Path-Scoped Commits"
section to use 2-space indentation (instead of 4) so markdownlint MD007 passes:
adjust the two nested list items ("Commit tracked files with:" and "Add and
commit new files explicitly:") and their fenced bash code blocks to align with
2-space nesting (e.g., two spaces before the hyphen and two spaces further for
the code fence lines), leaving the content of the code blocks unchanged.
🧹 Nitpick comments (1)
prompts/agents/CONSTRAINTS.md (1)

2-5: Optional: vary repeated “DO NOT” phrasing.

Minor readability tweak—four consecutive bullets start the same way. Consider mixing phrasing for scanability.

Comment on lines +11 to +19
- **Path-Scoped Commits**: Commit only the files you modified.
- Commit tracked files with:
```bash
git commit -m "<scoped message>" -- path/to/file1 path/to/file2
```
- Add and commit new files explicitly:
```bash
git add path/to/new/file && git commit -m "<message>"
```
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix list indentation to satisfy markdownlint (MD007).

The nested list items are indented by 4 spaces; markdownlint expects 2 here.

Proposed fix
-    - Commit tracked files with:
-        ```bash
-        git commit -m "<scoped message>" -- path/to/file1 path/to/file2
-        ```
-    - Add and commit new files explicitly:
-        ```bash
-        git add path/to/new/file && git commit -m "<message>"
-        ```
+  - Commit tracked files with:
+    ```bash
+    git commit -m "<scoped message>" -- path/to/file1 path/to/file2
+    ```
+  - Add and commit new files explicitly:
+    ```bash
+    git add path/to/new/file && git commit -m "<message>"
+    ```
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- **Path-Scoped Commits**: Commit only the files you modified.
- Commit tracked files with:
```bash
git commit -m "<scoped message>" -- path/to/file1 path/to/file2
```
- Add and commit new files explicitly:
```bash
git add path/to/new/file && git commit -m "<message>"
```
- **Path-Scoped Commits**: Commit only the files you modified.
- Commit tracked files with:
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

12-12: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)


16-16: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

🤖 Prompt for AI Agents
In `@prompts/agents/CONSTRAINTS.md` around lines 11 - 19, Update the nested list
under the "Path-Scoped Commits" section to use 2-space indentation (instead of
4) so markdownlint MD007 passes: adjust the two nested list items ("Commit
tracked files with:" and "Add and commit new files explicitly:") and their
fenced bash code blocks to align with 2-space nesting (e.g., two spaces before
the hyphen and two spaces further for the code fence lines), leaving the content
of the code blocks unchanged.

@codecov
Copy link

codecov bot commented Jan 20, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 48.63%. Comparing base (566c0c0) to head (a60c7ae).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #515   +/-   ##
==========================================
  Coverage      48.63%   48.63%           
  Complexity       474      474           
==========================================
  Files             65       65           
  Lines           2204     2204           
  Branches         312      312           
==========================================
  Hits            1072     1072           
  Misses          1001     1001           
  Partials         131      131           
Flag Coverage Δ
unittests 48.63% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@kingargyle kingargyle merged commit 61d765f into develop Feb 7, 2026
5 checks passed
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