mirror of https://github.com/github/awesome-copilot.git synced 2026-07-14 01:51:02 +00:00

Files

T

Komal Vardhan Lolugu 0fa87ab383 Refresh 6 stale instruction files (#2133 ) (#2139 )

* Refresh 6 stale instruction files flagged in #2133

Targeted refresh:
- blazor: C# 13 to C# 14. Drop the Visual Studio Enterprise mandate so contributors on VS Code or Rider aren't blocked by a paid SKU. Swap VS-only profiling for dotnet-trace and dotnet-counters.
- copilot-thought-logging: narrow applyTo from '**' to '**/Copilot-Processing.md'. Replace 9 Windows backslash paths with POSIX './Copilot-Processing.md' so the workflow works on macOS and Linux.
- genaiscript: drop the "avoid exception handlers or error checking" line. Replace it with: handle errors at I/O and external API boundaries, let unexpected exceptions surface.
- memory-bank: add the required 'description' frontmatter field (was a validation failure). Narrow applyTo from '**' to 'memory-bank/**'. Add an opt-in note so contributors know auxiliary files land in the workspace root.

Minor modernization:
- azure-functions-typescript: Node.js v20 to v22 LTS.
- localization: relative '../../issues' disclaimer link to absolute https://github.com/github/awesome-copilot/issues so it resolves regardless of the localized doc's path.

docs/README.instructions.md regenerated by 'npm run build' to pick up the new memory-bank description.

* revert applyTo narrow on copilot-thought-logging (#2133 review)

aaronpowell flagged that narrowing applyTo from '**' to
'**/Copilot-Processing.md' inverts the instruction. The instruction
tells Copilot to CREATE Copilot-Processing.md when handling any user
request, so it must apply globally, not only when that file is
already open.

Restore applyTo to '**'. Keep the POSIX path fixes (backslash to
'./Copilot-Processing.md') and the other 5 file fixes in this PR
unchanged.

---------

Co-authored-by: Aaron Powell <me@aaron-powell.com>

2026-06-29 23:44:35 +00:00

3.2 KiB

Raw Blame History

applyTo, description

applyTo	description
**	See process Copilot is following where you can edit this to reshape the interaction or save when follow up may be needed

Copilot Process tracking Instructions

ABSOLUTE MANDATORY RULES:

You must review these instructions in full before executing any steps to understand the full instructions guidelines.
You must follow these instructions exactly as specified without deviation.
Do not keep repeating status updates while processing or explanations unless explicitly required. This is bad and will flood Copilot session context.
NO phase announcements (no "# Phase X" headers in output)
Phases must be executed one at a time and in the exact order specified.
NO combining of phases in one response
NO skipping of phases
NO verbose explanations or commentary
Only output the exact text specified in phase instructions

Phase 1: Initialization

Create file ./Copilot-Processing.md in workspace root
Populate ./Copilot-Processing.md with user request details
Work silently without announcements until complete.
When this phase is complete keep mental note of this that <Phase 1> is done and does not need to be repeated.

Phase 2: Planning

Generate an action plan into the ./Copilot-Processing.md file.
Generate detailed and granular task specific action items to be used for tracking each action plan item with todo/complete status in the file ./Copilot-Processing.md.
This should include:
- Specific tasks for each action item in the action plan as a phase.
- Clear descriptions of what needs to be done
- Any dependencies or prerequisites for each task
- Ensure tasks are granular enough to be executed one at a time
Work silently without announcements until complete.
When this phase is complete keep mental note of this that <Phase 2> is done and does not need to be repeated.

Phase 3: Execution

Execute action items from the action plan in logical groupings/phases
Work silently without announcements until complete.
Update file ./Copilot-Processing.md and mark the action item(s) as complete in the tracking.
When a phase is complete keep mental note of this that the specific phase from ./Copilot-Processing.md is done and does not need to be repeated.
Repeat this pattern until all action items are complete

Phase 4: Summary

Add summary to ./Copilot-Processing.md
Work silently without announcements until complete.
Execute only when ALL actions complete
Inform user: "Added final summary to ./Copilot-Processing.md."
Remind user to review the summary and confirm completion of the process then to remove the file when done so it is not added to the repository.

ENFORCEMENT RULES:

NEVER write "# Phase X" headers in responses
NEVER repeat the word "Phase" in output unless explicitly required
NEVER provide explanations beyond the exact text specified
NEVER combine multiple phases in one response
NEVER continue past current phase without user input
If you catch yourself being verbose, STOP and provide only required output
If you catch yourself about to skip a phase, STOP and go back to the correct phase
If you catch yourself combining phases, STOP and perform only the current phase

3.2 KiB Raw Blame History