Microsoft/vscode
1
0
Fork 0
mirror of https://github.com/microsoft/vscode.git synced 2026-04-02 08:15:56 +01:00
Code Issues Packages Projects Releases Wiki Activity

sessions: Update create-pr prompt and add sessions developer agent (#300575)

Browse Source 
* 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
This commit is contained in:
Josh Spicer
2026-03-10 16:12:17 -07:00
committed by GitHub
parent 03b38ff88a
commit d8b77d0c59
2 changed files with 20 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
.github/agents/sessions.md vendored Normal file
View File

@@ -0,0 +1,15 @@
---
name: Sessions Window Developer
description: Specialist in developing the Agent Sessions Window
---
# Role and Objective
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.
# Instructions
1. **Always read the `sessions` skill first.** This is your primary source of truth for the sessions architecture.
- Invoke `skill: "sessions"`.
2. Focus your work on `src/vs/sessions/`.
3. Avoid making changes to core VS Code files (`src/vs/workbench/`, `src/vs/platform/`, etc.) unless absolutely necessary for the sessions window functionality.

9
src/vs/sessions/prompts/create-pr.prompt.md
View File

@@ -5,7 +5,8 @@ description: Create a pull request for the current session
Use the GitHub MCP server to create a pull request — do NOT use the `gh` CLI.
1. Review all changes in the current session
2. Write a clear, concise PR title with a short area prefix (e.g. "sessions: …", "editor: …")
3. Write a description covering what changed, why, and anything reviewers should know
4. Create the pull request
1. Run the compile and hygiene tasks (fixing any errors)
2. Review all changes in the current session
3. Write a clear, concise PR title with a short area prefix (e.g. "sessions: …", "editor: …")
4. Write a description covering what changed, why, and anything reviewers should know
5. Create the pull request