Skip to content

Add documentation for GitHub Copilot instruction types and skills [co…#14155

Open
andrewscfc wants to merge 2 commits into
latestfrom
copilot-guidance
Open

Add documentation for GitHub Copilot instruction types and skills [co…#14155
andrewscfc wants to merge 2 commits into
latestfrom
copilot-guidance

Conversation

@andrewscfc

Copy link
Copy Markdown
Contributor

…pilot]

Resolves JIRA: NA

Summary

I have struggled to find a suitable doc covering copilot-instructions.md vs. skills so this is a prompt generated doc to give guidance to engineers on instruction and skill use.

I have tried to ensure real docs are cited so we can be assured the guidance is accurate, please double check this in review.

Useful Links

Comment on lines +29 to +31
### A note on `AGENTS.md`

You may also see an `AGENTS.md` file referenced elsewhere. It is a cross-tool instructions file designed to be recognized by multiple AI agents, including non-Copilot tools. For our work, prefer `.github/copilot-instructions.md`: it serves the same always-on, repository-wide purpose for Copilot and has broader, more reliable support across Copilot tools (including Copilot code review). Use `.github/copilot-instructions.md` as the single source of repository-wide instructions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We need to stick to one of these, we currently have both, and it can cause issues https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions#custom-instructions-in-use

I'm leaning more towards the generic widely supported AGENTS.md file instead of the copilot one, there's literally no difference

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It claims AGENTS.md is ignored by copilot reviews so that's one argument against?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@HarveyPeachey HarveyPeachey Jun 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Which means there might be some context confusion currently for the robot

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

One argument for standardising on copilot-instructions is that (for now) Agents.md colocated with code is experimental; so there is no supported mechanism to do instructions scoped to individual files or directories with Agents.md, we can though do this with copilot-instructions (we are not allowed to use experimental copilot features as a reminder).

So it would make sense to use the same approach for repo wide and file/directory specific instructions with copilot-instructions.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

That's fine if we're gonna use that feature, let's just stick to one as currently there's going to be clashing context issues at the moment, lets delete AGENTS.md

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.

2 participants