Conversation
There was a problem hiding this comment.
Pull request overview
Updates the Copilot /init skill prompt to improve clarity and tighten the workflow guidance for generating/updating agent customization files (follow-up to the earlier generalization work in #309020).
Changes:
- Clarifies the optional argument behavior and reinforces “customizations only” scope.
- Improves wording/grammar around the invocation and completion instructions.
- Updates workflow guidance text (including referencing the
agent-customizationskill).
Show a summary per file
| File | Description |
|---|---|
| extensions/copilot/assets/prompts/skills/init/SKILL.md | Refines /init skill instructions and workflow wording for creating/updating customization files. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 2
|
|
||
| 3. **Generate or merge** | ||
| - New file: Prefern AGENTS.md over `.github/copilot-instructions.md`. If the user already has one of these files, update it instead of creating a new one. If both exist, update both. | ||
| - New file: Prefer AGENTS.md over `.github/copilot-instructions.md`. If the user already has one of these files, update it instead of creating a new one. |
There was a problem hiding this comment.
Step 3 now omits guidance for the case where both AGENTS.md and .github/copilot-instructions.md are present. Without explicitly saying to update both (or explaining which one is authoritative), the /init workflow becomes ambiguous and may lead to only one file being updated, causing divergence.
| - New file: Prefer AGENTS.md over `.github/copilot-instructions.md`. If the user already has one of these files, update it instead of creating a new one. | |
| - Agent instructions file: If neither file exists, create `AGENTS.md` rather than `.github/copilot-instructions.md`. If exactly one of these files exists, update the existing file instead of creating a new one. If both `AGENTS.md` and `.github/copilot-instructions.md` exist, treat `AGENTS.md` as the authoritative file and update both files to keep them aligned. |
| Explore the codebase to get a good understanding of the project and its conventions, and then create or update the relevant chat customization files to help AI coding agents be productive in this codebase. | ||
|
|
||
| When complete, give the user table of the added or modified chat customization files, along with a short explanation why this file is useful for the AI coding agents. | ||
| When complete, print a table of the added or modified chat customization files, along with a short explanation why this file is useful to the AI coding agents. |
There was a problem hiding this comment.
Minor grammar: “a short explanation why this file is useful…” reads awkwardly; consider “a short explanation of why this file is useful…”.
| When complete, print a table of the added or modified chat customization files, along with a short explanation why this file is useful to the AI coding agents. | |
| When complete, print a table of the added or modified chat customization files, along with a short explanation of why this file is useful to the AI coding agents. |
Followup on #309020