Skip to content

fix: replace VS Code Copilot tool names with valid Claude Code tools#534

Open
xiaolai wants to merge 1 commit intodavila7:mainfrom
xiaolai:fix/nlpm-invalid-agent-tool-names
Open

fix: replace VS Code Copilot tool names with valid Claude Code tools#534
xiaolai wants to merge 1 commit intodavila7:mainfrom
xiaolai:fix/nlpm-invalid-agent-tool-names

Conversation

@xiaolai
Copy link
Copy Markdown

@xiaolai xiaolai commented Apr 22, 2026

Automated audit: This PR was generated by NLPM, a natural language programming linter, running via claude-code-action. Please evaluate the diff on its merits.

Bug

Three agents in cli-tool/components/agents/devops-infrastructure/ declare VS Code Copilot tool names in their tools: frontmatter field — names that are not valid in Claude Code:

Agent Invalid tools declared
devops-expert.md codebase, edit/editFiles, terminalCommand, search, githubRepo, runCommands, runTasks
se-gitops-ci-specialist.md codebase, edit/editFiles, terminalCommand, search, githubRepo
terraform-iac-reviewer.md codebase, edit/editFiles, terminalCommand, search, githubRepo

These tool names originated in GitHub Copilot's agent definition format and are not recognized by Claude Code. At runtime, Claude Code silently ignores unknown tool names, so these agents receive no tools at all — they cannot read files, run commands, or do any work.

Fix

Replace the invalid tool names with the correct Claude Code equivalents:

# Before
tools: codebase, edit/editFiles, terminalCommand, search, githubRepo, runCommands, runTasks

# After
tools: Read, Write, Edit, Bash, Glob, Grep

Valid Claude Code tool names: Read, Write, Edit, MultiEdit, Bash, Glob, Grep, WebSearch, WebFetch, Agent, Task, TodoWrite

The selected tools (Read, Write, Edit, Bash, Glob, Grep) are appropriate for DevOps/infrastructure work: reading config files, editing IaC, running shell commands, and searching codebases.

Why it matters

Without this fix, a user who loads any of these three agents gets an agent with zero tool access — it cannot read a single file or execute any command, silently rendering it non-functional. The agent body contains extensive, high-quality DevOps guidance that deserves working tool access.


Summary by cubic

Replaced VS Code Copilot tool names with valid Claude Code tools so three DevOps agents get working tool access. This fixes agents being non-functional due to ignored tools.

  • Bug Fixes
    • Updated tools to Read, Write, Edit, Bash, Glob, Grep in: devops-expert.md, se-gitops-ci-specialist.md, terraform-iac-reviewer.md.
    • Area: components (cli-tool/components/agents/devops-infrastructure/).
    • No new components; no docs/components.json regeneration needed.
    • No new environment variables or secrets.

Written for commit 0417c54. Summary will update on new commits.

Three devops-infrastructure agents listed VS Code Copilot tool names
(codebase, edit/editFiles, terminalCommand, search, githubRepo,
runCommands, runTasks) which are not valid in Claude Code. At runtime,
Claude Code silently ignores unknown tool names, so these agents
received no tools at all.

Replaced with the correct Claude Code tool names: Read, Write, Edit,
Bash, Glob, Grep — appropriate for infrastructure review/automation
work done by these agents.

Files fixed:
- devops-expert.md
- se-gitops-ci-specialist.md
- terraform-iac-reviewer.md

Co-Authored-By: Claude Code <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 22, 2026

@claude is attempting to deploy a commit to the Daniel Avila's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added the review-pending Component PR awaiting maintainer review label Apr 22, 2026
@github-actions
Copy link
Copy Markdown
Contributor

👋 Thanks for contributing, @xiaolai!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

  1. 🤖 Automated security audit runs and posts results on this PR.
  2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
  3. Merge — once approved, your PR is merged to main.
  4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
  5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

  • Check the Security Audit comment below for any issues to fix.
  • Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 3 files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-pending Component PR awaiting maintainer review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants