refactor: Remove focus_areas parameter from agent tool #541
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR removes the
focus_areasparameter from the MCP agent tool and all related components throughout the automation plugin. This simplifies the interface by reducing parameter complexity while maintaining functionality through the existingconstraintsparameter.Changes Made
Core Components
focus_areasfrom input schema and implementationfocus_areasparameter fromprepare_context()andexplore()methodsfocus_areasextraction and passing to agent methodsfocus_areasfrom operation inputs and prompt buildingConfiguration
focus_areasinput definition from workflowDocumentation
focus_areasreferencesTests
focus_areasassertionsconstraintsinstead offocus_areasfocus_areasTesting
All automation plugin tests pass successfully:
Migration Path
Users who were using
focus_areascan achieve similar functionality by using theconstraintsparameter in workflows. For example:Before:
After:
Impact
focus_areasparameter is no longer availableconstraintsparameter🤖 Generated with Claude Code