Consider reducing the size of standard copilot instructions. The long documengt might flood copilot token space without any additonal benefit.
i.e. I do not see any reason to add an Contents section at the start of the document.
In additon I would suggest to move compex instructions for testing and README into extra files as its ok to provide some standard information hwo a README.md should be built. But its definitly not desired that copilot tries to restructure README.md at every problem fixing. Some is valid for testing. When initially requesting testing those instructiosn are needed and ok. But it's not desired that copilozt tries to add tesing modules for any fix if currently no testing is present and there's no explizit request to add testing.
Consider reducing the size of standard copilot instructions. The long documengt might flood copilot token space without any additonal benefit.
i.e. I do not see any reason to add an Contents section at the start of the document.
In additon I would suggest to move compex instructions for testing and README into extra files as its ok to provide some standard information hwo a README.md should be built. But its definitly not desired that copilot tries to restructure README.md at every problem fixing. Some is valid for testing. When initially requesting testing those instructiosn are needed and ok. But it's not desired that copilozt tries to add tesing modules for any fix if currently no testing is present and there's no explizit request to add testing.