Discussion - Possible Tools: code actions, diff, changes, supertypes, subtypes, incoming/outgoing calls

[biegehydra]

I would like to hear others thoughts about implementing each of these features. Whether its worth it or not. I will provide my thoughts in a separate comment and please feel free to provide any reasoning for why we should/shouldn't add each of these.

vscode.provideSupertypes - Compute supertypes for an item

• item - A type hierarchy item
• (returns) - A promise that resolves to an array of TypeHierarchyItem-instances

vscode.provideSubtypes - Compute subtypes for an item

• item - A type hierarchy item
• (returns) - A promise that resolves to an array of TypeHierarchyItem-instances

vscode.provideIncomingCalls - Compute incoming calls for an item

• item - A call hierarchy item
• (returns) - A promise that resolves to an array of CallHierarchyIncomingCall-instances

vscode.provideOutgoingCalls - Compute outgoing calls for an item

• item - A call hierarchy item
• (returns) - A promise that resolves to an array of CallHierarchyOutgoingCall-instances

vscode.diff - Opens the provided resources in the diff editor to compare their contents.

• left - Left-hand side resource of the diff editor
• right - Right-hand side resource of the diff editor
• title - Human readable title for the diff editor
• options - (optional) Either the column in which to open, or editor options (see vscode.TextDocumentShowOptions)

vscode.changes - Opens a list of resources in the changes editor to compare their contents.

• title - Human readable title for the changes editor
• resourceList - List of resources to compare

vscode.executeCodeActionProvider - Execute code action provider.

• uri - Uri of a text document
• rangeOrSelection - Range in a text document. Some refactoring provider requires Selection object.
• kind - (optional) Code action kind to return code actions for
• itemResolveCount - (optional) Number of code actions to resolve (too large numbers slow down code actions)
• (returns) - A promise that resolves to an array of Command-instances.

[biegehydra]

• Super/Subtypes - Is this redundant to get_type_hierarchy or get_type_definition?
• Incoming/Outgoing Calls - Is this redundant to get_call_hierarchy?
• Diff - I know there are other git specific mcp tools but I don't use them and think this would be useful. Maybe I could create an option to be able to enable/disable tools
• Changes - Could be super useful for some workflows. Like having a LLM review all its changes at the end
• Code Action Provider - Also huge. Almost every language has linters that provide automatic refactors/code-actions that can be performed. It's a little annoying that you need to provide a rangeOrSelection though. I would want to see all the suggested refactors for an entire document or project. That may be achievable by providing entire document as selection

[armaanahluwalia]

Hey. I just wanted to congratulate you on the awesome work you're doing. ❤️

I stumbled upon this project to speed up my LLM code edits via Cline. For me the most valuable addition would be replace across files ( either via VScode native built in or something custom ). Either one would be a game changer. 🙏

[biegehydra]

Replace already exists 💪. You mean rename right?

[armaanahluwalia]

Ahh yes just saw it 🙌
LLM wasn't picking it up for some reason. Will try it out! This is legendary stuff