docs: streamline copilot setup check prompt Phase 1 #11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary\nRefined Phase 1 core files assessment in copilot-setup-check prompt to reduce cognitive load. Consolidated 10 repetitive bullets into 7 grouped categories (presence, clarity/context, conflict detection, enforcement markers, improvement actions, pruning redundancies, reinforcement opportunities).\n\n### Changes\n- Frontmatter normalized (agent/name/argument-hint/tools list) removing write-capable editFiles tool.\n- Grouped granular suggestion bullets into concise thematic categories for faster scanning.\n- Preserved original intent (existence check, structure, clarity, conflicts, enforcement, improvement, reinforcement) without semantic loss.\n\n### Rationale\nImproves readability and reduces analysis overhead for evaluators using the prompt. Keeps alignment with SSOT policies in .github/copilot-instructions.md by referencing XML semantic tags and conflict detection.\n\n### Impact\nNo runtime or CI impact; documentation prompt only. Downstream agents retain same evaluation semantics while spending less time parsing.\n\n### Next Ideas (Not Included)\n- Add explicit scoring rubric (1–10)\n- Add link/anchor validation step\n- Provide sample executive summary template\n\n### Checklist\n- [x] Conventional commit message\n- [x] Prompt lint: frontmatter valid YAML\n- [x] Alignment with SSOT maintained\n\n