Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-04-13 19:55:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(agents): replace deprecated tool names with official namespaced equivalents 🤖🤖🤖 (#1382)

Browse Source 
Update tools lists in tdd-red, tdd-green, tdd-refactor, and github-actions-expert
agents to use the current VS Code Copilot built-in tool names.

Old names were silently ignored by VS Code (documented behaviour: 'If a given
tool is not available when using the custom agent, it is ignored.').

Tool name mapping applied:
- github          → github/*
- findTestFiles   → search/fileSearch
- runTests        → execute/runTests
- runCommands     → execute/runInTerminal
- terminalCommand → execute/runInTerminal
- codebase        → search/codebase
- filesystem      → read/readFile
- problems        → read/problems
- testFailure     → execute/testFailure
- terminalLastCommand → read/terminalLastCommand
- githubRepo      → github/*

Also added missing tools present in the current VS Code tool reference:
- execute/getTerminalOutput
- read/terminalSelection

Additionally, generalised C#-specific content in TDD agents to be polyglot,
covering JavaScript/TypeScript (Jest/Vitest), Python (pytest), Java/Kotlin
(JUnit 5), and C# (.NET) — making the agents useful to the broader community.

Reference: https://code.visualstudio.com/docs/copilot/reference/copilot-vscode-features#_chat-tools

Co-authored-by: Ming <oncwnuAUeYAFR4UGlq8BEJq8Jy-k@git.weixin.qq.com>
This commit is contained in:
ming
2026-04-13 09:02:14 +08:00
committed by GitHub
parent 30ed357edc
commit e37cd3123f
4 changed files with 26 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
agents/tdd-red.agent.md
View File

@@ -1,7 +1,7 @@
---
description: "Guide test-first development by writing failing tests that describe desired behaviour from GitHub issue context before implementation exists."
name: "TDD Red Phase - Write Failing Tests First"
tools: ["github", "findTestFiles", "edit/editFiles", "runTests", "runCommands", "codebase", "filesystem", "search", "problems", "testFailure", "terminalLastCommand"]
tools: ["github/*", "search/fileSearch", "edit/editFiles", "execute/runTests", "execute/runInTerminal", "execute/getTerminalOutput", "execute/testFailure", "read/readFile", "read/terminalLastCommand", "read/terminalSelection", "read/problems", "search/codebase"]
---
# TDD Red Phase - Write Failing Tests First
@@ -34,17 +34,19 @@ Focus on writing clear, specific failing tests that describe the desired behavio
### Test Quality Standards
- **Descriptive test names** - Use clear, behaviour-focused naming like `Should_ReturnValidationError_When_EmailIsInvalid_Issue{number}`
- **Descriptive test names** - Use clear, behaviour-focused naming like `returnsValidationError_whenEmailIsInvalid_issue{number}` (adapt casing to your language convention)
- **AAA Pattern** - Structure tests with clear Arrange, Act, Assert sections
- **Single assertion focus** - Each test should verify one specific outcome from issue criteria
- **Edge cases first** - Consider boundary conditions mentioned in issue discussions
### C# Test Patterns
### Test Patterns (Polyglot)
- Use **xUnit** with **FluentAssertions** for readable assertions
- Apply **AutoFixture** for test data generation
- Implement **Theory tests** for multiple input scenarios from issue examples
- Create **custom assertions** for domain-specific validations outlined in issue
- **JavaScript/TypeScript**: Use **Jest** or **Vitest** with `describe`/`it` blocks and `expect` assertions
- **Python**: Use **pytest** with descriptive function names and `assert` statements
- **Java/Kotlin**: Use **JUnit 5** with **AssertJ** for fluent assertions
- **C#/.NET**: Use **xUnit** or **NUnit** with **FluentAssertions**
- Apply parameterised/data-driven tests for multiple input scenarios from issue examples
- Create shared test utilities for domain-specific validations outlined in issue
## Execution Guidelines