Update tool metadata

.github/chatmodes/CodeReviewer.chatmode.md

@@ -1,6 +1,6 @@
 ---
 description: 'Code Reviewer Mode'
-tools: ['codebase', 'search', 'usages', 'problems', 'changes']
+tools: ['search/codebase', 'search', 'usages', 'problems', 'changes']
 ---
 
 <!-- This is an example Chat Mode, rather than a canonical one -->

.github/chatmodes/Developer.chatmode.md

@@ -1,7 +1,6 @@
 ---
 description: 'Developer Mode'
-
-tools: ['codebase', 'usages', 'problems', 'changes', 'testFailure', 'terminalSelection', 'terminalLastCommand', 'openSimpleBrowser', 'fetch', 'findTestFiles', 'searchResults', 'githubRepo', 'todos', 'editFiles', 'runNotebooks', 'search', 'new', 'runCommands', 'runTasks']
+tools: ['search/codebase', 'usages', 'problems', 'changes', 'testFailure', 'runCommands/terminalSelection', 'runCommands/terminalLastCommand', 'openSimpleBrowser', 'fetch', 'findTestFiles', 'search/searchResults', 'githubRepo', 'todos', 'edit/editFiles', 'runNotebooks', 'search', 'new', 'runCommands', 'runTasks']
 ---
 
 <!-- This is an example Chat Mode, rather than a canonical one -->

.github/chatmodes/Documentation.chatmode.md

@@ -1,6 +1,6 @@
 ---
 description: 'Documentation Mode'
-tools: ['codebase', 'search', 'editFiles', 'usages', 'problems', 'changes', 'fetch']
+tools: ['search/codebase', 'search', 'edit/editFiles', 'usages', 'problems', 'changes', 'fetch']
 ---
 
 <!-- This is an example Chat Mode, rather than a canonical one -->

.github/chatmodes/Planner.chatmode.md

@@ -1,6 +1,6 @@
 ---
 description: 'Planner Mode'
-tools: ['codebase', 'editFiles', 'fetch', 'get_file_contents', 'runCommands', 'search', 'usages']
+tools: ['search/codebase', 'edit/editFiles', 'fetch', 'github/get_file_contents', 'runCommands', 'search', 'usages']
 ---
 
 <!-- This is an example Chat Mode, rather than a canonical one -->

.github/prompts/copilot-setup-check.prompt.md

@@ -40,6 +40,7 @@ This evaluation will assess:
 ## Analysis Process
 
 ### Phase 1: Core Files Assessment
+
 1. **Check AGENTS.md existence and quality**
    - Verify presence and structure
    - Assess clarity of repository context
@@ -54,6 +55,7 @@ This evaluation will assess:
    - Verify XML semantic tags for critical requirements
 
 ### Phase 2: Advanced Configuration Review
+
 3. **Analyze custom chatmodes**
    - Count and categorize existing chatmodes
    - Assess relevance to project needs

.github/prompts/write-adr.prompt.md

@@ -1,7 +1,7 @@
 ---
 mode: 'agent'
 description: 'Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.'
-tools: ['codebase', 'usages', 'problems', 'changes', 'terminalSelection', 'terminalLastCommand', 'fetch', 'searchResults', 'editFiles', 'search', 'runCommands']
+tools: ['search/codebase', 'usages', 'problems', 'changes', 'runCommands/terminalSelection', 'runCommands/terminalLastCommand', 'fetch', 'search/searchResults', 'edit/editFiles', 'search', 'runCommands']
 ---
 
 <!-- Top-level section: Defines the primary task (create an ADR) and sets expectations for structured, AI-optimised output. Techniques: imperative directives, variable interpolation (${input:...}) to parameterise the decision title, and a rule to request more context when inputs are insufficient. -->

.github/prompts/write-docs.prompt.md

@@ -1,6 +1,6 @@
 ---
 description: "Instructions for writing coding documentation"
-tools: ['codebase', 'editFiles', 'fetch']
+tools: ['search/codebase', 'edit/editFiles', 'fetch']
 ---
 <!-- Top-level section: Defines the documentation-writing task and the step-by-step workflow the assistant should follow. Techniques: imperative verbs, numbered list for clear sequencing, and explicit prompts to elicit scope, audience, and content. -->
 # Write Documentation

.github/prompts/write-ears-spec.prompt.md

@@ -1,7 +1,7 @@
 ---
 mode: 'agent'
 description: 'Create a specification using the EARS format'
-tools: ['codebase', 'usages', 'changes', 'terminalSelection', 'terminalLastCommand', 'fetch', 'searchResults', 'githubRepo', 'todos', 'editFiles', 'search', 'runCommands', 'runTasks']
+tools: ['search/codebase', 'usages', 'changes', 'runCommands/terminalSelection', 'runCommands/terminalLastCommand', 'fetch', 'search/searchResults', 'githubRepo', 'todos', 'edit/editFiles', 'search', 'runCommands', 'runTasks']
 ---
 
 <!-- Top-level section: Establishes the overall task for the assistant and the high-level interaction pattern. Emphasis techniques: imperative phrasing ("Guide"), numbered steps for clarity, and explicit prompts to ensure structured, concise inputs. -->

.github/prompts/write-prd.prompt.md

@@ -1,7 +1,7 @@
 ---
 mode: 'agent'
 description: 'Create a Product Requirements Document (PRD) using the repository PRD template and structured guidance for both humans and automation.'
-tools: ['codebase', 'usages', 'changes', 'editFiles', 'fetch', 'search', 'searchResults', 'runCommands', 'todos']
+tools: ['search/codebase', 'usages', 'changes', 'edit/editFiles', 'fetch', 'search', 'search/searchResults', 'runCommands', 'todos']
 ---
 
 <!-- Top-level purpose: Define the PRD creation task and guardrails. Techniques: clear title, imperative voice, and branch/filename conventions to guide edits. -->

.github/pull_request_template.md

@@ -1,13 +1,16 @@
 # Pull Request
 
 ## Summary
+
 - What is changing and why?
 
 ## Links
+
 - Plan/TODO item: (e.g., plans/TODO.md row or issue link)
 - ADR/PRD/design doc: (link to docs/ADRs or docs/PRDs or docs/design)
 
 ## Quality & Policy Checks
+
 - [ ] Branch/PR rules followed (see `.github/copilot-instructions.md`)
 - [ ] Tests added/updated; critical paths & errors at 100% (see Quality Policy)
 - [ ] Docs updated (if applicable)
@@ -16,4 +19,5 @@
 ## Screenshots / Demos (optional)
 
 ## Notes for Reviewers
+
 - Risks, trade-offs, or areas needing extra attention

.github/workflows/docs-lint.yml

@@ -15,6 +15,7 @@ jobs:
         with:
           globs: |
             **/*.md
+            !.github/**/*.md
           config: .markdownlint.jsonc
 
   link-check: