From 24351ecc6eb801a429fba45bf8eaebba0c7d3083 Mon Sep 17 00:00:00 2001 From: Kaleb Luedtke Date: Sun, 3 May 2026 16:56:01 -0500 Subject: [PATCH 1/3] Add custom instruction for handling memory updates --- .github/instructions/copilot-memory.md | 30 ++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 .github/instructions/copilot-memory.md diff --git a/.github/instructions/copilot-memory.md b/.github/instructions/copilot-memory.md new file mode 100644 index 0000000000..dbdb211a75 --- /dev/null +++ b/.github/instructions/copilot-memory.md @@ -0,0 +1,30 @@ +--- +applyTo: "**" +--- + +# Copilot Memory + +Preferences and conventions learned from working in this repository. Any conventions that are not explicitly mentioned here should be inferred from the codebase. + +## How to Handle Corrections + +When a user corrects you on terminology, naming conventions, workflow preferences, or any other practice that applies repository-wide (not just to the current task), follow these steps: + +1. **Recognize the correction.** A correction has occurred when the user tells you that something you said, named, or did is wrong or should be done differently — especially if it involves consistent patterns such as naming conventions, terminology, architectural practices, or tool usage. + +2. **Assess the scope.** Ask yourself: *Would other contributors to this repository benefit from knowing this? Would a future agent session make the same mistake without this guidance?* If yes, it is a candidate for shared repository memory (this file). If the correction is personal to this user (e.g., a workflow preference or output style), it is a candidate for user memory instead. + +3. **Ask the user before storing.** Do not silently write to either location. Instead, ask: + + > "Should I remember this correction for the future? If so, should I add it to the **repository memory** (`copilot-memory.md`) so all contributors' agents benefit, or as a **user memory** (via the memory skill) that applies only to your sessions?" + + Offer both options clearly and let the user decide. + +4. **Act on the answer.** + - If **repository memory**: add a concise, unambiguous entry under the appropriate section of this file (`copilot-memory.md`) and commit it. + - If **user memory**: call the `store_memory` tool with a clear `fact`, a `reason` explaining when it applies, and a `citations` reference to this conversation or the relevant file. + - If **neither**: acknowledge and move on without storing. + +## Terminology + +- Use **Packaged** and **Unpackaged** (not "Package context" / "Non-package context") when referring to the two WinGet execution contexts. From 4df7f2463a093645f8573ba24d073d909702b532 Mon Sep 17 00:00:00 2001 From: Kaleb Luedtke Date: Sun, 3 May 2026 17:10:16 -0500 Subject: [PATCH 2/3] Ensure file is loaded as instructions file --- .../{copilot-memory.md => copilot-memory.instructions.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/instructions/{copilot-memory.md => copilot-memory.instructions.md} (100%) diff --git a/.github/instructions/copilot-memory.md b/.github/instructions/copilot-memory.instructions.md similarity index 100% rename from .github/instructions/copilot-memory.md rename to .github/instructions/copilot-memory.instructions.md From 2ca13aeeab3404ede3674f3e00673a1b92269346 Mon Sep 17 00:00:00 2001 From: Kaleb Luedtke Date: Sun, 3 May 2026 17:11:09 -0500 Subject: [PATCH 3/3] Adjust for new file name --- .github/instructions/copilot-memory.instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/instructions/copilot-memory.instructions.md b/.github/instructions/copilot-memory.instructions.md index dbdb211a75..41b481d92e 100644 --- a/.github/instructions/copilot-memory.instructions.md +++ b/.github/instructions/copilot-memory.instructions.md @@ -21,7 +21,7 @@ When a user corrects you on terminology, naming conventions, workflow preference Offer both options clearly and let the user decide. 4. **Act on the answer.** - - If **repository memory**: add a concise, unambiguous entry under the appropriate section of this file (`copilot-memory.md`) and commit it. + - If **repository memory**: add a concise, unambiguous entry under the appropriate section of this file (`copilot-memory.instructions.md`) and commit it. - If **user memory**: call the `store_memory` tool with a clear `fact`, a `reason` explaining when it applies, and a `citations` reference to this conversation or the relevant file. - If **neither**: acknowledge and move on without storing.