release_20251120

.claude/commands/start-task.md

@@ -11,10 +11,10 @@ argument-hint: GitHub Issue URL
 
 - Check if the user provided a Github Issue URL as argument (for example Example: `https://github.com/<owner>/<repo>/issues/123`). If not, ask for it.
 - Parse the URL to extract `{owner}`, `{repo}`, and `{issue_number}`.
-- Verify that the Issue number corresponds to an existing Issue in the GitHub repository by using the specific GitHub MCP Server configured for this repository.
+- Verify that the Issue number corresponds to an existing Issue in the GitHub repository by using the gh cli configured for this repository.
 - If the Issue does not exist, inform the user and abort.
 - Checkout a branch `issues/[issue-number]` starting from the source branch.
-- Fetch the Issue description and full comment list using the GitHub MCP server.
+- Fetch the Issue description and full comment list using the gh cli
 
 ## Phase 1: Initial Implementation
 - Start the csharp-dev subagent passing the Issue description and comments as context

.github/prompts/brainstorm.prompt.md

@@ -1,5 +1,5 @@
 ---
-mode: agent
+agent: agent
 model: GPT-4.1 (copilot)
 description: AI ideation partner for technical and product brainstorming
 ---

.github/prompts/releasemanager.prompt.md

@@ -1,7 +1,8 @@
 ---
-mode: agent
+agent: agent
 model: GPT-4.1 (copilot)
 description: Generate release notes from a GitHub Pull Request URL
+tools: [runCommands]
 ---
 
 ## Goal
@@ -13,21 +14,21 @@ Generate clean and structured **release notes** from a given GitHub Pull Request
 
 ## Expected Behavior
 1. Parse the URL to extract `{owner}`, `{repo}`, and `{pull_number}`.
-2. Use the **GitHub MCP server** tools to:
+2. Use the **gh cli** to:
   - Retrieve the list of commits for the Pull Request.
   - Optionally fetch the PR title, description, author, merge date, and linked issues.
   - Gather metadata such as changed files, labels, and additions/deletions if available.
 3. Classify commits following **Conventional Commits** style:
   - `feat`, `fix`, `perf`, `docs`, `refactor`, `test`, `chore`
 4. Highlight any `BREAKING CHANGE` entries.
 5. Summarize and format the information as a structured **Markdown release note**.
-6. Use the **GitHub MCP server** to update the pull request description with the release notes.
+6. Use the **gh cli** to update the pull request description with the release notes.
 
 ## Remember
 - Focus on clarity, conciseness, and relevance.
 - Proceed without asking permissions.
 - Do not create file output
-- Use GitHub MCP server always
+- Use gh cli always
 
 ## Output Format (Markdown)
 
@@ -44,10 +45,9 @@ Generate clean and structured **release notes** from a given GitHub Pull Request
 
 
 #### 🔗 References
-- PR: {url}
 - Linked Issues: {#issue_numbers}
 
-Note: add at the end of the body: "Created by AI 🤖"
+Note: add at the end of the body: "Created by AI"
 
 ## Style Guidelines
 - Use concise, clear sentences in **active voice**.

.github/prompts/storytelling.prompt.md

@@ -1,5 +1,5 @@
 ---
-mode: agent
+agent: agent
 model: GPT-4.1 (copilot)
 description: User story generator that validates and closes all open points before producing final immutable stories
 ---
@@ -27,7 +27,7 @@ Before writing user stories:
 - Ask the user to answer them clearly
 - Confirm understanding back to the user
 - Only proceed when the user explicitly says requirements are finalized and approved
-- Request to user if you create the issue on github by using the github MCP server
+- Request to user if you create the issue on github by using the gh cli
 
 ### Output Phase
 
@@ -67,9 +67,9 @@ User Story template:
 - Never produce stories without explicit user approval
 - This agent is convergent: no ideation
 
-### GitHub MCP Integration
+### GitHub Integration
 - If user approves: 
-  1. create an issue on GitHub using the MCP server
+  1. create an issue on GitHub using the gh cli
     - Title: "🤖 Implement User Story: <short summary>"
     - Body: Full content of the user story markdown file + add at the end of the body: "Created by AI 🤖"
     - Do not use labels or assignees

CLAUDE.md

@@ -138,8 +138,8 @@ dotnet test
 
 Do not skip these steps - they catch issues early and ensure code quality.
 
-## MCP Server
-When you need to get issues or PR from GitHub, use the specific GitHub MCP Server configured for this repository.
+## Github Interactions
+When you need to get issues or PR from GitHub, use the gh cli configured for this repository.
 
 ## Remember
-Do not use gh cli or GitHub API directly. Always use the MCP server for GitHub interactions.
+Always use the gh cli for GitHub interactions.