Skip to content

Conversation

@SrishJ23
Copy link
Contributor

Fixes #311

This PR documents the memory agent in CUSTOM-AGENTS.md.

  • Added a new Utility Agents category
  • Documented the memory agent purpose, workflow, and constraints
  • Followed existing formatting and structure

@SrishJ23 SrishJ23 requested a review from a team as a code owner January 30, 2026 17:36
@SrishJ23
Copy link
Contributor Author

Hi @WilliamBerryiii,

I’ve added the memory agent to CUSTOM-AGENTS.md and included its details following the existing format.

Please let me know if any changes are needed. Thanks!

@SrishJ23
Copy link
Contributor Author

Thanks for pointing this out — you’re right.

The doc-ops entry was added by mistake and is not related to this PR.
I’ll review the file, revert any unintended changes, and update the PR to focus only on adding the memory agent, following the existing agent patterns.

Thanks for the guidance.

@SrishJ23
Copy link
Contributor Author

Thanks for the guidance.

I’ve restored the original content and updated the PR to only add the memory agent, following the existing structure and patterns.

@codecov-commenter
Copy link

codecov-commenter commented Feb 1, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 52.41%. Comparing base (15f7185) to head (e1004f8).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #359      +/-   ##
==========================================
- Coverage   52.44%   52.41%   -0.04%     
==========================================
  Files          17       17              
  Lines        3110     3110              
==========================================
- Hits         1631     1630       -1     
- Misses       1479     1480       +1     
Flag Coverage Δ
pester 52.41% <ø> (-0.04%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes

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

@WilliamBerryiii
Copy link
Member

Thanks for the contribution @SrishJ23 ... merging now.

@WilliamBerryiii
Copy link
Member

@katriendg, Can you review the changes? I'm also going to file an issue that maybe consider lightening this document to just enumerate the groupings of agents and create detailed agent/workflow explanations in the /docs directory. Thoughts?


**Creates:** Architecture Decision Records:

* `.copilot-tracking/adrs/{{topic-name}}-draft.md` (working draft)
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we keep the original, this is relevant information, same on the line 201, keep the (final location) wording


**Creates:** Installation configuration and tracking:

* `.hve-tracking.json` (for agent copy tracking)
Copy link
Contributor

Choose a reason for hiding this comment

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

Please keep the (for agent copy tracking) on line 294

**Creates:** Installation configuration and tracking:

* `.hve-tracking.json` (for agent copy tracking)
* Settings updates in `.vscode/settings.json`
Copy link
Contributor

Choose a reason for hiding this comment

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

here also keep Settings updates in wording, it is relevant.

@katriendg
Copy link
Contributor

@WilliamBerryiii I like the idea of moving the detailed documentations into the docs folder and keeping this one short.

@katriendg
Copy link
Contributor

@SrishJ23 Thanks for the changes - I did see a few changes that we should revert, small additions of wording that we want to keep. Once you revert those back we can approve and merge!

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.

docs: add memory agent to CUSTOM-AGENTS.md

4 participants