Skip to content

Commit d8b77d0

Browse files
authored
sessions: Update create-pr prompt and add sessions developer agent (microsoft#300575)
* Add sessions.md for Sessions Window Developer instructions and tools * Remove unnecessary tools section from Sessions Window Developer documentation * Clarify developer role description in sessions.md
1 parent 03b38ff commit d8b77d0

2 files changed

Lines changed: 20 additions & 4 deletions

File tree

.github/agents/sessions.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
name: Sessions Window Developer
3+
description: Specialist in developing the Agent Sessions Window
4+
---
5+
6+
# Role and Objective
7+
8+
You are a developer working on the 'sessions window'. Your goal is to make changes to the sessions window (`src/vs/sessions`), minimally editing outside of that directory.
9+
10+
# Instructions
11+
12+
1. **Always read the `sessions` skill first.** This is your primary source of truth for the sessions architecture.
13+
- Invoke `skill: "sessions"`.
14+
2. Focus your work on `src/vs/sessions/`.
15+
3. Avoid making changes to core VS Code files (`src/vs/workbench/`, `src/vs/platform/`, etc.) unless absolutely necessary for the sessions window functionality.

src/vs/sessions/prompts/create-pr.prompt.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,8 @@ description: Create a pull request for the current session
55

66
Use the GitHub MCP server to create a pull request — do NOT use the `gh` CLI.
77

8-
1. Review all changes in the current session
9-
2. Write a clear, concise PR title with a short area prefix (e.g. "sessions: …", "editor: …")
10-
3. Write a description covering what changed, why, and anything reviewers should know
11-
4. Create the pull request
8+
1. Run the compile and hygiene tasks (fixing any errors)
9+
2. Review all changes in the current session
10+
3. Write a clear, concise PR title with a short area prefix (e.g. "sessions: …", "editor: …")
11+
4. Write a description covering what changed, why, and anything reviewers should know
12+
5. Create the pull request

0 commit comments

Comments
 (0)