Skip to content

Add /investigate chat command #270274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
+32 −0
Draft

Add /investigate chat command #270274

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a373801
v1 /investigate slash command
benvillalobos Oct 7, 2025
ae7e67d
Update .github/prompts/investigate.prompt.md
benvillalobos Oct 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions .github/prompts/investigate.prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
---
mode: agent
tools: ['search', 'github/github-mcp-server/get_commit', 'github/github-mcp-server/get_issue', 'github/github-mcp-server/get_issue_comments', 'github/github-mcp-server/get_pull_request', 'github/github-mcp-server/get_pull_request_diff', 'github/github-mcp-server/get_pull_request_files', 'github/github-mcp-server/get_pull_request_review_comments', 'github/github-mcp-server/get_pull_request_reviews', 'github/github-mcp-server/get_pull_request_status', 'changes', 'fetch', 'todos']
---
Your goal is to perform an investigation of a given issue and return with investigation notes. For this you need to:
1. Understand the context of the bug or feature by reading the issue description and comments.
2. Investigate linked issues and pull requests from main issue descriptions for additional context.
3. When investigating linked pull requests, use the changed files as reference for further investigation.
4. Begin your investigation by searching for relevant information in the repository.

Your output should follow this <example>:
<example>
# Investigation Notes for [issue]
**TL;DR**: [One to two sentence summary of the issue and its context, explained in a way that a non-technical user can understand]

## Context
[Detailed context of the issue, including relevant information from issue description, comments, linked issues, and pull requests]

## Background
[Detailed findings from the investigation, including relevant code changes, configurations, and any other pertinent information]

## Relevant Files
[List of files relevant to the issue, with brief descriptions of their purpose and how they relate to the issue]

## Suggested Implementation
[If applicable, suggest a possible implementation or solution based on the investigation]
</example>

## Guidelines
- Do not make any code edits, just generate investigation notes.
- Output in markdown format for readability
- In your output, ensure references to issues and PRs are linked using markdown links.
Loading