Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new Agent Skill (triage) to guide AI-assisted triage of incoming EF Core bug reports, focusing on producing minimal standalone repros and posting findings back to GitHub issues.
Changes:
- Introduces a new triage skill document with a recommended repro console template.
- Adds step-by-step guidance for minimizing repros, validating regressions, and posting results.
You can also share your feedback on Copilot code review. Take the survey.
There was a problem hiding this comment.
Pull request overview
Adds a new Agent Skill (triage) intended to guide AI-assisted triage of incoming EF Core bug reports, focusing on producing a minimal standalone repro, validating regressions, and posting findings back to GitHub issues.
Changes:
- Introduces a new
.agents/skills/triage/SKILL.mdskill with a suggested minimal console repro template. - Adds workflow guidance for narrowing repros, checking regression status, and searching for duplicates.
- Specifies formatting expectations for posting triage results back to issues (heading, disclaimer,
<details>wrapper).
You can also share your feedback on Copilot code review. Take the survey.
.agents/skills/triage/SKILL.md
Outdated
|
|
||
| # EF Bug Report Triage | ||
|
|
||
| You are an agent helping to triage and reproduce incoming issues on the Entity Framework Core repository; your task is to read the issue in question (provided as input in the prompt), as well as any linked issues/code/resources, and to try to arrive at a minimal repro. User-submitted issues frequently provide only fragmentary information and code snippets, forcing you to try to fill in the missing information in the effort to create a minimal repro; valuable information is frequently provided in free-form text, which you need to integrate into the repro as code. |
There was a problem hiding this comment.
Reword this in terms of a skill that an agent uses instead of changing the agent purpose. Otherwise, make this a custom agent
There was a problem hiding this comment.
I guess I'm moving away from custom agents as they're Copilot-only, and I'd rather do something more standard (even though it's unlikely someone will specifically want to triage an EF issue with another agent architecture).
Skills seems to be the more modern thing where everything's going in any case - even though I still think there's a bit of needless context pollution by including this skill's name/description whenever I work on EF, and also the needless non-deterministic invocation of the skill (compared to manually selecting custom agents from a dropdown).
Let me know if you have any thoughts/preferences.
There was a problem hiding this comment.
Pull request overview
Adds a new Copilot agent skill for triaging EF Core bug reports (focused on creating minimal repros), and adjusts the Copilot setup workflow’s SQL Server connection string to use a non-system database.
Changes:
- Update Copilot setup steps to export a SQL Server connection string targeting
Database=test. - Add a new
.agents/skills/triage/SKILL.mdskill with guidance for reproducing and minimizing bug report repros.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| .github/workflows/copilot-setup-steps.yml | Updates the exported SQL Server connection string for the agent session. |
| .agents/skills/triage/SKILL.md | Introduces a triage skill with a minimal repro template and posting guidance. |
You can also share your feedback on Copilot code review. Take the survey.
No description provided.