Merge branch 'staged' into staged

Author: mubaidr

agents/new-relic-incident-response.agent.md

@@ -1,16 +1,63 @@
 ---
 name: New Relic Incident Response Agent
 description: Identify and fix production issues by correlating New Relic observability data with code changes. Analyze alerts, transaction traces, error analytics, and deployments to find root causes and suggest code fixes.
-model: gpt-4.1
+model:
+   - GPT-4.1
+   - GPT-5.4
+   - Claude Sonnet 4.6
 tools:
-   - new-relic-mcp-server
+   - new-relic-mcp-server/*
    - github
 ---
+# Context
+You have access to New Relic's MCP server tools through the users environment. If needed, you can use OAuth to access the MCP server instead of the users credentials.
 
-# New Relic Incident Response & Debugging Agent - System Prompt
+This repository should have access to information around how this application and codebase is instrumented with New Relic. You can find information on the context by using newrelic.ini directory in this repository. Wherever possible, correlate the results of the incident to the specific Application present in this repository.
+
+# New Relic Incident Response & Debugging Agent - Main Goal
 
 Your goal is to help engineers rapidly triage and resolve production incidents by correlating New Relic observability data with code changes. You act as an expert incident responder who uses alerts, transaction traces, error analytics, and recent deployment data to identify root causes and suggest code fixes.
 
+## MCP Server Configuration requirement
+
+This custom agent depends on a configured New Relic MCP server. The server registration in your MCP settings must be discoverable to the agent and should use the configured server name `new-relic-mcp-server`.
+
+Before starting an investigation:
+
+- Confirm that the New Relic MCP server is available in the current session
+- Prefer the configured `new-relic-mcp-server` MCP server when retrieving alerts, traces, errors, deployments, and NRQL results
+- If the server is unavailable or misconfigured, stop and tell the engineer exactly which MCP server is missing instead of guessing
+- If your environment uses a different server name, update the tool prefixes in this agent profile to match the configured name
+- If the MCP settings use `include-tags`, only tools in those tag groups will actually be exposed to the agent even if they are listed in `tools:` here
+- Keep `.vscode/mcp.json` aligned with this profile when using the agent in VS Code.
+- If possible prompt the user for OAuth authentication to the MCP server if not already authenticated, so that you can access the New Relic data needed for incident response.
+
+Expected MCP coverage:
+
+- Alert violations and policy details
+- Change tracking and deployment markers
+- Transaction traces and performance data
+- Error analytics and stack traces
+- Distributed tracing
+- NRQL query execution
+
+Example MCP settings alignment:
+
+```json
+{
+   "servers": {
+      "new-relic-mcp-server": {
+         "url": "https://mcp.newrelic.com/mcp/",
+         "type": "http",
+         "headers": {
+            "api-key": "${COPILOT_MCP_NEW_RELIC_API_KEY}",
+            "include-tags": "discovery,data-access,alerting,incident-response,performance-analytics,advanced-analysis"
+         }
+      }
+   }
+}
+```
+
 ## Core Capabilities
 
 You assist engineers with rapid incident response by:
@@ -23,6 +70,14 @@ You assist engineers with rapid incident response by:
 
 **Code Remediation**: Suggesting specific code fixes, rollback strategies, or mitigation approaches based on the observability data
 
+# How this agent should operate
+
+When an engineer is investigating a production incident, they will ask you questions about the issue. You should use the New Relic MCP server tools to retrieve relevant observability data (alerts, traces, errors, deployments) and correlate it with recent code changes from GitHub. Your responses should help the engineer understand the root cause of the incident and suggest specific code changes or mitigation strategies to resolve it.
+
+Start the process by going through phase 1 (Incident Assessment) to understand the alert and establish a timeline. Then ask if the user wants to proceed to phase 2 (Root Cause Investigation) to analyze traces, errors, and changes. Finally, if the root cause is identified, ask if they want to proceed to phase 3 (Code Analysis and Fix) where you can suggest specific code changes. Always confirm with the engineer before making any code changes or suggesting fixes. Your role is to assist and guide the engineer through the incident response process, not to take unilateral action.
+
+For clarity, before running large complex time consuming queries, check with the user on which account they are investigating, and which issues they want to focus on. Always ask for confirmation before running queries that could take a long time or return large amounts of data.
+
 ## Steps to Follow
 
 ### Phase 1: Incident Assessment
@@ -256,4 +311,4 @@ File: `src/repositories/UserRepository.java`
 - Add integration test that runs queries against production-sized dataset
 - Add alert for slow query duration (>500ms)
 - Add code review checklist item: "All database queries have WHERE clauses"
-```
+```

docs/README.skills.md

@@ -250,6 +250,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [onboard-context-matic](../skills/onboard-context-matic/SKILL.md)<br />`gh skills install github/awesome-copilot onboard-context-matic` | Interactive onboarding tour for the context-matic MCP server. Walks the user through what the server does, shows all available APIs, lets them pick one to explore, explains it in their project language, demonstrates model_search and endpoint_search live, and ends with a menu of things the user can ask the agent to do. USE FOR: first-time setup; "what can this MCP do?"; "show me the available APIs"; "onboard me"; "how do I use the context-matic server"; "give me a tour". DO NOT USE FOR: actually integrating an API end-to-end (use integrate-context-matic instead). | None |
 | [oo-component-documentation](../skills/oo-component-documentation/SKILL.md)<br />`gh skills install github/awesome-copilot oo-component-documentation` | Create or update standardized object-oriented component documentation using a shared template plus mode-specific guidance for new and existing docs. | `assets/documentation-template.md`<br />`references/create-mode.md`<br />`references/update-mode.md` |
 | [openapi-to-application-code](../skills/openapi-to-application-code/SKILL.md)<br />`gh skills install github/awesome-copilot openapi-to-application-code` | Generate a complete, production-ready application from an OpenAPI specification | None |
+| [optimize-simplicite-logs](../skills/optimize-simplicite-logs/SKILL.md)<br />`gh skills install github/awesome-copilot optimize-simplicite-logs` | capability to parse Simplicité logs from a raw `.txt` file, filter fields to reduce noise, and output the result as structured JSON. | `scripts/SimpliciteLog2Json.ps1`<br />`scripts/simplicite-log2json.py` |
 | [pdftk-server](../skills/pdftk-server/SKILL.md)<br />`gh skills install github/awesome-copilot pdftk-server` | Skill for using the command-line tool pdftk (PDFtk Server) for working with PDF files. Use when asked to merge PDFs, split PDFs, rotate pages, encrypt or decrypt PDFs, fill PDF forms, apply watermarks, stamp overlays, extract metadata, burst documents into pages, repair corrupted PDFs, attach or extract files, or perform any PDF manipulation from the command line. | `references/download.md`<br />`references/pdftk-cli-examples.md`<br />`references/pdftk-man-page.md`<br />`references/pdftk-server-license.md`<br />`references/third-party-materials.md` |
 | [penpot-uiux-design](../skills/penpot-uiux-design/SKILL.md)<br />`gh skills install github/awesome-copilot penpot-uiux-design` | Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools. Use this skill when: (1) Creating new UI/UX designs for web, mobile, or desktop applications, (2) Building design systems with components and tokens, (3) Designing dashboards, forms, navigation, or landing pages, (4) Applying accessibility standards and best practices, (5) Following platform guidelines (iOS, Android, Material Design), (6) Reviewing or improving existing Penpot designs for usability. Triggers: "design a UI", "create interface", "build layout", "design dashboard", "create form", "design landing page", "make it accessible", "design system", "component library". | `references/accessibility.md`<br />`references/component-patterns.md`<br />`references/platform-guidelines.md`<br />`references/setup-troubleshooting.md` |
 | [performance-review-writer](../skills/performance-review-writer/SKILL.md)<br />`gh skills install github/awesome-copilot performance-review-writer` | Draft performance reviews, self-assessments, peer reviews, and upward feedback in your own voice. Analyzes your contributions, emails, and meeting history via WorkIQ, then produces honest, impact-focused drafts using the STAR format. USE FOR: write my performance review, draft self-assessment, peer review, 360 feedback, annual review, mid-year review, upward feedback, write review for colleague, performance appraisal. | None |

skills/optimize-simplicite-logs/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: optimize-simplicite-logs
+description: capability to parse Simplicité logs from a raw `.txt` file, filter fields to reduce noise, and output the result as structured JSON.
+---
+
+# Optimize Simplicite Logs
+
+This skill provides the capability to parse Simplicité logs from a raw `.txt` file, filter fields to reduce noise, and output the result as structured JSON. This is critical for optimizing AI context size (saving ~56% of tokens) and providing structured, predictable data for troubleshooting.
+
+## When to Use This Skill
+
+Use this skill when you need to:
+- Analyze user-provided Simplicité log files in `.txt` format.
+- Avoid ingesting massive raw log files into your context window.
+- Extract structured fields (like `timestamp`, `level`, `body`) from verbose multi-line log output.
+
+**IMPORTANT:** Instead of directly reading a raw `.txt` log file provided by the user using file read tools, you **must** use one of the log converter scripts (PowerShell or Python) to parse the file into a JSON format first, optionally extracting only the fields needed.
+
+## Prerequisites
+
+- Access to either the PowerShell script (`/scripts/SimpliciteLog2Json.ps1`) or the Python script (`/scripts/simplicite-log2json.py`).
+
+## Core Capabilities
+
+### 1. Context Optimization
+Reduces the tokens consumed by large Simplicité logs by extracting only relevant log fields (e.g. `body`, `timestamp`, `level`) and discarding non-relevant structural log data (like `app`, `endpoint`, `contextPath`).
+
+### 2. Multi-line Support
+Properly captures stack traces and multiline errors inside the `body` field of the JSON structure, which a simple text search might miss.
+
+### 3. Stdout Support
+If no output path is provided for the JSON file (e.g. omitting `--output` or `-Output`), the parsed JSON will be printed directly to stdout, allowing you to pipe the output to other tools.
+
+## Output Summary
+
+After processing, the tool prints a summary to stderr (or console):
+```
+Processed: 123 entries, Skipped: 2 entries
+```
+
+## Usage Examples
+
+### Example 1: Python Version (Recommended)
+Convert a log file to JSON, keeping only the most important fields:
+```sh
+python /absolute/path/to/skills/optimize-simplicite-logs/scripts/simplicite-log2json.py <input.txt> --include timestamp,level,body --output <output.json>
+```
+
+### Example 2: PowerShell Version
+```powershell
+/python /absolute/path/to/skills/optimize-simplicite-logs/scripts/SimpliciteLog2Json.ps1 -InputPath "<input.txt>" -Output "<output.json>" -Include "body,timestamp,level"
+```
+
+After generating the `<output.json>`, you can safely read the resulting file to perform your analysis.
+
+## Guidelines
+
+1. **Always Convert First:** Never directly read `.txt` log files from Simplicité using standard text reading tools. Always convert them to JSON using the available scripts.
+2. **Filter Fields:** Use `--include` (Python) or `-Include` (PowerShell) to restrict fields to what is absolutely necessary to diagnose the issue (usually `timestamp,level,body`).
+3. **Available Fields:** The fields you can filter include: `timestamp`, `app`, `level`, `endpoint`, `contextPath`, `event`, `user`, `class`, `function`, `rowId`, `body`.
+
+## Common Patterns
+
+### Pattern: Fast Contextual Troubleshooting
+```sh
+# 1. Run the script to generate a minified JSON output in the current directory
+python /absolute/path/to/skills/optimize-simplicite-logs/scripts/simplicite-log2json.py logs.txt --include timestamp,level,body --output logs_minified.json
+
+# 2. Then read logs_minified.json to understand the context.
+```
+
+## Limitations
+
+- The parser depends on a fixed regex pattern that matches the standard Simplicité log output. If the log format has been heavily customized, parsing might fail or degrade.

skills/optimize-simplicite-logs/scripts/SimpliciteLog2Json.ps1

@@ -0,0 +1,153 @@
+param (
+    [Parameter(Mandatory=$true)]
+    [string]$InputPath,
+
+    [string]$Output,
+
+    [string]$Include,
+
+    [string]$Exclude
+)
+
+# Valid fields
+$ValidFields = @("timestamp", "app", "level", "endpoint", "contextPath", "event", "user", "class", "function", "rowId", "body")
+
+# Function to check if a field is valid
+function Test-ValidField {
+    param([string]$Field)
+    return $ValidFields -contains $Field
+}
+
+# Verify that -Include and -Exclude are not both used
+if ($Include -and $Exclude) {
+    Write-Error "Error: -Include and -Exclude cannot be used together."
+    exit 1
+}
+
+# Initialize field variables
+$IncludeFields = $null
+$ExcludeFields = $null
+
+# Validate fields provided in Include/Exclude
+if ($Include) {
+    $IncludeFields = $Include -split "," | ForEach-Object { $_.Trim() }
+    foreach ($field in $IncludeFields) {
+        if (-not (Test-ValidField $field)) {
+            Write-Error "Error: Invalid field '$field'. Valid fields: $($ValidFields -join ', ')"
+            exit 1
+        }
+    }
+}
+
+if ($Exclude) {
+    $ExcludeFields = $Exclude -split "," | ForEach-Object { $_.Trim() }
+    foreach ($field in $ExcludeFields) {
+        if (-not (Test-ValidField $field)) {
+            Write-Error "Error: Invalid field '$field'. Valid fields: $($ValidFields -join ', ')"
+            exit 1
+        }
+    }
+}
+
+# Check that the input file exists
+if (-not (Test-Path $InputPath)) {
+    Write-Error "Error: File $InputPath does not exist."
+    exit 1
+}
+# Read the file and normalize line endings
+# Group raw lines into log entries where a new entry starts with a timestamp.
+$raw = Get-Content -Path $InputPath -Raw
+$raw = $raw -replace "`r`n","`n" -replace "`r","`n"
+$lines = $raw -split "`n"
+
+$entryTexts = @()
+$buffer = ""
+$skippedLines = 0
+
+foreach ($line in $lines) {
+    if ($line -eq $null) { continue }
+    if ($line.Trim().Length -eq 0) { continue }
+
+    if ($line -match '^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2},\d{3}') {
+        if ($buffer -ne "") { $entryTexts += $buffer }
+        $buffer = $line
+    } else {
+        # Continuation line: attach to current buffer if present, otherwise skip
+        if ($buffer -eq "") {
+            $skippedLines++
+            continue
+        } else {
+            $buffer += "`n" + $line
+        }
+    }
+}
+
+if ($buffer -ne "") { $entryTexts += $buffer }
+
+$entries = @()
+$processed = 0
+$skippedMalformed = 0
+
+foreach ($entryText in $entryTexts) {
+    $parts = $entryText -split '\|'
+    if ($parts.Count -ge 12) {
+        # Trim only the first 11 fields; preserve the body (may contain pipes/newlines)
+        for ($i=0; $i -le 10; $i++) { $parts[$i] = $parts[$i].Trim() }
+
+        $body = ($parts[11..($parts.Count - 1)] -join '|')
+
+        $entry = @{
+            timestamp   = $parts[0]
+            app         = $parts[1]
+            level       = $parts[2]
+            endpoint    = $parts[4]
+            contextPath = $parts[5]
+            event       = $parts[6]
+            user        = $parts[7]
+            class       = $parts[8]
+            function    = $parts[9]
+            rowId       = $parts[10]
+            body        = $body
+        }
+
+        # Apply include/exclude filters
+        if ($IncludeFields -and $IncludeFields.Count -gt 0) {
+            $filteredEntry = @{}
+            foreach ($field in $IncludeFields) {
+                if ($entry.ContainsKey($field)) {
+                    $filteredEntry[$field] = $entry[$field]
+                } else {
+                    $filteredEntry[$field] = $null
+                }
+            }
+            $entry = $filteredEntry
+        }
+        elseif ($ExcludeFields -and $ExcludeFields.Count -gt 0) {
+            foreach ($field in $ExcludeFields) {
+                if ($entry.ContainsKey($field)) {
+                    $entry.PSObject.Properties.Remove($field)
+                }
+            }
+        }
+
+        $entries += $entry
+        $processed++
+    } else {
+        $skippedMalformed++
+    }
+}
+
+$skipped = $skippedLines + $skippedMalformed
+
+# Convert to JSON (compact)
+$json = $entries | ConvertTo-Json -Depth 10 -Compress
+
+# Write output
+if ($Output) {
+    Set-Content -Path $Output -Value $json -Encoding UTF8
+    Write-Host "Output written to $Output"
+} else {
+    $json
+}
+
+Write-Host "Processed: $processed entries, Skipped: $skipped entries"