You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three lifecycle event handlers in cli/src/cmd/copilot/commands/listen.go - handlePostProvision, handlePreDeploy, and handlePostDeploy - are registered with the extension framework but are no-op stubs (just return nil with "Could..." comments). They occupy extension lifecycle slots without providing functionality, giving a false impression of coverage.
The get_project_context MCP tool in cli/src/cmd/copilot/commands/mcp.go (lines 134-147) is a placeholder stub that returns hardcoded instructional text ("Check azure.yaml…") rather than calling the azd gRPC client to fetch real project context. All other gRPC-backed tools use newAzdClient() properly; this one silently diverges.
The create_checkpoint MCP tool in cli/src/cmd/copilot/commands/mcp.go (lines 149-166) does not actually create a checkpoint - it just formats and returns a string with the description and phase. The real checkpoint.SaveWithOptions() API exists in cli/src/internal/checkpoint/checkpoint.go but is never called, making the tool's name misleading.
The list_agents and list_skills MCP tools (and MCP resource handlers) in mcp.go use hardcoded lists (7 agents, 5 skills) that are stale and inconsistent with the actual embedded assets: there are 16 agent .md files in assets/agents/ and 10+ skill directories in assets/skills/. The assets.ListAgents() and assets.ListSkills() APIs exist and should be used instead.
code quality audit
cli/src/cmd/copilot/commands/listen.go-handlePostProvision,handlePreDeploy, andhandlePostDeploy- are registered with the extension framework but are no-op stubs (justreturn nilwith "Could..." comments). They occupy extension lifecycle slots without providing functionality, giving a false impression of coverage.get_project_contextMCP tool incli/src/cmd/copilot/commands/mcp.go(lines 134-147) is a placeholder stub that returns hardcoded instructional text ("Check azure.yaml…") rather than calling the azd gRPC client to fetch real project context. All other gRPC-backed tools usenewAzdClient()properly; this one silently diverges.create_checkpointMCP tool incli/src/cmd/copilot/commands/mcp.go(lines 149-166) does not actually create a checkpoint - it just formats and returns a string with the description and phase. The realcheckpoint.SaveWithOptions()API exists incli/src/internal/checkpoint/checkpoint.gobut is never called, making the tool's name misleading.list_agentsandlist_skillsMCP tools (and MCP resource handlers) inmcp.gouse hardcoded lists (7 agents, 5 skills) that are stale and inconsistent with the actual embedded assets: there are 16 agent.mdfiles inassets/agents/and 10+ skill directories inassets/skills/. Theassets.ListAgents()andassets.ListSkills()APIs exist and should be used instead.Automated analysis - 4 finding(s)