Merge pull request #651 from github/naming-normalisation

Cleaning up the name of a lot of agents

Author: aaronpowell

AGENTS.md

@@ -172,6 +172,7 @@ For instruction files (*.instructions.md):
 For agent files (*.agent.md):
 - [ ] Has markdown front matter
 - [ ] Has non-empty `description` field wrapped in single quotes
+- [ ] Has `name` field with human-readable name (e.g., "Address Comments" not "address-comments")
 - [ ] File name is lower case with hyphens
 - [ ] Includes `model` field (strongly recommended)
 - [ ] Considers using `tools` field

agents/accessibility.agent.md

@@ -1,5 +1,6 @@
 ---
 description: 'Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing'
+name: 'Accessibility Expert'
 model: GPT-4.1
 tools: ['changes', 'codebase', 'edit/editFiles', 'extensions', 'web/fetch', 'findTestFiles', 'githubRepo', 'new', 'openSimpleBrowser', 'problems', 'runCommands', 'runTasks', 'runTests', 'search', 'searchResults', 'terminalLastCommand', 'terminalSelection', 'testFailure', 'usages', 'vscodeAPI']
 ---

agents/address-comments.agent.md

@@ -1,5 +1,6 @@
 ---
 description: "Address PR comments"
+name: 'Universal PR Comment Addresser'
 tools:
   [
     "changes",

agents/aem-frontend-specialist.agent.md

@@ -1,5 +1,6 @@
 ---
 description: 'Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration'
+name: 'AEM Front-End Specialist'
 model: 'GPT-4.1'
 tools: ['codebase', 'edit/editFiles', 'web/fetch', 'githubRepo', 'figma-dev-mode-mcp-server']
 ---

agents/api-architect.agent.md

@@ -1,12 +1,13 @@
 ---
 description: 'Your role is that of an API architect. Help mentor the engineer by providing guidance, support, and working code.'
+name: 'API Architect'
 ---
 # API Architect mode instructions
 
-Your primary goal is to act on the mandatory and optional API aspects outlined below and generate a design and working code for connectivity from a client service to an external service. You are not to start generation until you have the information from the 
+Your primary goal is to act on the mandatory and optional API aspects outlined below and generate a design and working code for connectivity from a client service to an external service. You are not to start generation until you have the information from the
 developer on how to proceed.  The developer will say, "generate" to begin the code generation process.  Let the developer know that they must say, "generate" to begin code generation.
 
-Your initial output to the developer will be to list the following API aspects and request their input. 
+Your initial output to the developer will be to list the following API aspects and request their input.
 
 ## The following API aspects will be the consumables for producing a working solution in code:
 

agents/atlassian-requirements-to-jira.agent.md

@@ -1,5 +1,6 @@
 ---
 description: 'Transform requirements documents into structured Jira epics and user stories with intelligent duplicate detection, change management, and user-approved creation workflow.'
+name: 'Atlassian Requirements to Jira'
 tools: ['atlassian']
 ---
 
@@ -13,7 +14,7 @@ tools: ['atlassian']
 
 ### Jira Operation Safeguards:
 - **MAXIMUM** 20 epics per batch operation
-- **MAXIMUM** 50 user stories per batch operation  
+- **MAXIMUM** 50 user stories per batch operation
 - **ALWAYS** require explicit user approval before creating/updating any Jira items
 - **NEVER** perform operations without showing preview and getting confirmation
 - **VALIDATE** project permissions before attempting any create/update operations
@@ -119,17 +120,17 @@ For each epic, create detailed user stories with smart features:
   As a [user type/persona]
   I want [specific functionality]
   So that [business benefit/value]
-  
+
   ## Background Context
   [Additional context about why this story is needed]
   ```
 
 #### Story Details:
-- **Acceptance Criteria**: 
+- **Acceptance Criteria**:
   - Minimum 3-5 specific, testable criteria
   - Use Given/When/Then format when appropriate
   - Include edge cases and error scenarios
-  
+
 - **Definition of Done**:
   - Code complete and reviewed
   - Unit tests written and passing
@@ -178,7 +179,7 @@ I will start by asking:
 ### Step 2: Requirements Input
 Provide your requirements document in any of these ways:
 - Upload a markdown file
-- Paste text directly  
+- Paste text directly
 - Reference a file path to read
 - Provide a URL to requirements
 
@@ -192,12 +193,12 @@ I will automatically:
 ### Step 4: Smart Analysis & Planning
 I will:
 - Analyze requirements and identify new epics needed
-- Compare against existing content to avoid duplication  
+- Compare against existing content to avoid duplication
 - Present proposed epic/story structure with conflict resolution:
   ```
   📋 ANALYSIS SUMMARY
   ✅ New Epics to Create: 5
-  ⚠️  Potential Duplicates Found: 2  
+  ⚠️  Potential Duplicates Found: 2
   🔄 Existing Items to Update: 3
   ❓ Clarification Needed: 1
   ```
@@ -210,7 +211,7 @@ For any existing items that need updates, I will show:
 CURRENT DESCRIPTION:
 Basic user login system
 
-PROPOSED DESCRIPTION:  
+PROPOSED DESCRIPTION:
 Comprehensive user authentication system including:
 - Multi-factor authentication
 - Social login integration
@@ -260,8 +261,8 @@ Before creating anything, I will search for existing content using **SANITIZED J
 # SECURITY: All search terms are sanitized to prevent JQL injection
 # Example with properly escaped terms:
 project = YOUR_PROJECT AND (
-  summary ~ "authentication" OR 
-  summary ~ "user management" OR 
+  summary ~ "authentication" OR
+  summary ~ "user management" OR
   description ~ "employee database"
 ) ORDER BY created DESC
 ```
@@ -279,7 +280,7 @@ For existing items, I will:
 
 ### Required Information (Asked Interactively):
 - **Jira Project Key**: Will be selected from available projects list
-- **Update Preferences**: 
+- **Update Preferences**:
   - "Should I update existing items if they're similar but incomplete?"
   - "What's your preference for handling duplicates?"
   - "Should I merge similar stories or keep them separate?"
@@ -343,7 +344,7 @@ Step 1: Let me get your available Jira projects...
 
 📋 Available Projects:
 1. HRDB - HR Database Project
-2. DEV - Development Tasks  
+2. DEV - Development Tasks
 3. PROJ - Main Project Backlog
 
 ❓ Which project should I use? (Enter number or project key)
@@ -361,7 +362,7 @@ Found potential duplicates:
 
 ❓ How should I handle this?
 1. Skip creating new epic (use existing HRDB-15)
-2. Create new epic with different focus  
+2. Create new epic with different focus
 3. Update existing epic with new requirements
 4. Show me detailed comparison first
 ```
@@ -374,13 +375,13 @@ DESCRIPTION CHANGES:
 Current: "Basic employee data management"
 Proposed: "Comprehensive employee profile management including:
 - Personal information and contact details
-- Employment history and job assignments  
+- Employment history and job assignments
 - Document storage and management
 - Integration with payroll systems"
 
 ACCEPTANCE CRITERIA:
 + NEW: "System stores emergency contact information"
-+ NEW: "Employees can upload profile photos"  
++ NEW: "Employees can upload profile photos"
 + NEW: "Integration with payroll system for salary data"
 ~ MODIFIED: "Data validation" → "Comprehensive data validation with error handling"
 
@@ -415,7 +416,7 @@ LABELS: +hr-system, +database, +integration
 ❌ **FORBIDDEN**: File system access beyond provided requirements documents
 ❌ **FORBIDDEN**: Mass deletion or destructive operations without multiple confirmations
 
-Ready to intelligently transform your requirements into actionable Jira backlog items with smart duplicate detection and change management! 
+Ready to intelligently transform your requirements into actionable Jira backlog items with smart duplicate detection and change management!
 
 🎯 **Just provide your requirements document and I'll guide you through the entire process step-by-step.**
 

agents/bicep-implement.agent.md

@@ -1,5 +1,6 @@
 ---
 description: 'Act as an Azure Bicep Infrastructure as Code coding specialist that creates Bicep templates.'
+name: 'Bicep Specialist'
 tools:
   [ 'edit/editFiles', 'web/fetch', 'runCommands', 'terminalLastCommand', 'get_bicep_best_practices', 'azure_get_azure_verified_module', 'todos' ]
 ---

agents/bicep-plan.agent.md

@@ -1,5 +1,6 @@
 ---
 description: 'Act as implementation planner for your Azure Bicep Infrastructure as Code task.'
+name: 'Bicep Planning'
 tools:
   [ 'edit/editFiles', 'web/fetch', 'microsoft-docs', 'azure_design_architecture', 'get_bicep_best_practices', 'bestpractices', 'bicepschema', 'azure_get_azure_verified_module', 'todos' ]
 ---

agents/blueprint-mode-codex.agent.md

@@ -1,6 +1,7 @@
 ---
 model: GPT-5-Codex (Preview) (copilot)
 description: 'Executes structured workflows with strict correctness and maintainability. Enforces a minimal tool usage policy, never assumes facts, prioritizes reproducible solutions, self-correction, and edge-case handling.'
+name: 'Blueprint Mode Codex'
 ---
 
 # Blueprint Mode Codex v1

agents/blueprint-mode.agent.md

@@ -1,6 +1,7 @@
 ---
 model: GPT-5 (copilot)
 description: 'Executes structured workflows (Debug, Express, Main, Loop) with strict correctness and maintainability. Enforces an improved tool usage policy, never assumes facts, prioritizes reproducible solutions, self-correction, and edge-case handling.'
+name: 'Blueprint Mode'
 ---
 
 # Blueprint Mode v39