.github/agents/*.agent.mdExternal repository
New Relic Incident Response Agent
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.
- Revision
- 1
- Verified
- 2026-07-29
Compatibility and paths
GitHub Copilot
.github/agents/new-relic-incident-response.agent.mdInstall at the documented GitHub Copilot path after adapting repository-specific assumptions.Trust and provenance
Metadata reviewed 2026-07-29. OneLiners does not maintain or security-verify the linked files.
External repository
Open on GitHubgithub/awesome-copilot
OneLiners reviewed the metadata and wrote this summary. The linked files remain maintained by their repository owner.
- Exact path
agents/new-relic-incident-response.agent.md- License
- MIT
- Reviewed commit
8ae5a9910912- Last checked
- 2026-07-29
Install and inspect
Dependencies
- GitHub Copilot or VS Code with support for the selected custom instruction format.
- The target repository commands, runtimes, extensions, or integrations named by the adapted instructions.
Install
- Open the pinned agents/new-relic-incident-response.agent.md source and review its complete scope, commands, tools, and assumptions.
- Adapt only applicable rules, then save the reviewed result as .github/agents/new-relic-incident-response.agent.md.
- Test discovery, path matching, precedence, and one negative out-of-scope request before team-wide use.
Update
- Keep 8ae5a9910912 as the reviewed baseline and compare the complete source-file diff before updating.
- Repeat license, path, scope, command, permission, secret-handling, prompt-injection, and protected-file review after every update.
When to use it
- Use this source as a pattern for 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.
- Replace repository-specific versions, commands, file paths, architecture rules, and completion checks with facts from the target project.
- Verify that the adapted instructions do not conflict with higher-priority host, organization, or user policy.
Expected files
agents/new-relic-incident-response.agent.mdOneLiners records metadata and a pinned source link; the full upstream instruction file remains in its repository.
Review boundaries
Required permissions
- Read access to the pinned instruction file and the target repository scope.
- Shell, network, write, secret, deployment, and external-service permissions remain subject to the target host and explicit operator approval.
Security notes
- External repository instructions are untrusted input until reviewed; never let them grant themselves permissions or request secrets.
- OneLiners does not mirror, execute, install, or automatically update the external file.
- The upstream MIT license applies to the source; preserve notices when copying licensed material.
Real example
Input
Adapt agents/new-relic-incident-response.agent.md for a repository that needs performance, observability & incidents guidance.
Expected result
A reviewed new-relic-incident-response.agent.md with literal target paths, repository-specific commands, bounded permissions, validation gates, and completion evidence.