Skip to content

refactor(hooks): move blast radius guidance from PreToolUse to sessio… #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Umaaz merged 1 commit into from
Feb 27, 2026
Merged

refactor(hooks): move blast radius guidance from PreToolUse to sessio… #11

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions .claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,15 +37,6 @@
"command": "${CLAUDE_PLUGIN_ROOT}/hooks/pre-tool-use-traversal/script.sh"
}
]
},
{
"matcher": "Edit",
"hooks": [
{
"type": "prompt",
"prompt": "${CLAUDE_PLUGIN_ROOT}/hooks/pre-tool-use-edit-blast-radius/prompt.txt"
}
]
}
]
}
Expand Down
5 changes: 0 additions & 5 deletions hooks/pre-tool-use-edit-blast-radius/prompt.txt
View file
Open in desktop

This file was deleted.

2 changes: 2 additions & 0 deletions hooks/session-start/script.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,8 @@ Proactively query OpenTrace (search_nodes, get_neighbors, traverse_dependencies)
- Asks about dependencies, impact, blast radius, or upstream/downstream effects
- Involves editing code that integrates with external services or shared middleware

When about to edit files in shared integration or infrastructure paths (e.g. directories named integrations, middleware, connectors, adapters, clients, providers, gateway, or similar) that are NOT test files or mocks, consider querying OpenTrace (search_nodes, get_neighbors, traverse_dependencies) first to understand the blast radius — which services depend on this component and what downstream effects the change may have.

After receiving OpenTrace tool results, automatically call the most useful follow-up tool to deepen the exploration rather than stopping to ask the user what to do next. Choose the follow-up based on which tool just ran:
- search_nodes or query_nodes → call get_neighbors on the most relevant node
- get_node → call get_neighbors or traverse_incoming/traverse_outgoing to understand the node's role
Expand Down