feat: Add DestructiveHint to delete_project_item tool annotation #1665
+4
−2
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
Adds
DestructiveHint: trueannotation to thedelete_project_itemtool to be consistent with other delete operations that properly indicate destructive behavior.Changes
DestructiveHint: jsonschema.Ptr(true)todelete_project_itemtool inpkg/github/projects.goWhy This Matters
The
delete_project_itemtool permanently removes a project item, making it a destructive operation. Other delete tools in the codebase (delete_file,delete_workflow_run_logs) correctly have this annotation set. This ensures LLMs receive consistent semantic metadata about tool behavior:delete_fileReadOnlyHint: false, DestructiveHint: true✅delete_workflow_run_logsReadOnlyHint: false, DestructiveHint: true✅delete_project_itemReadOnlyHint: false❌ → FixedTesting
jsonschema.Ptr(true)pattern as other destructive tools🤖 Generated with Claude Code