check_section_delete_safe
Check if a documentation section is safe to delete before removal. It returns a read-only verdict with ranked blockers and a recommended action.
Instructions
Composite preflight: is this section safe to delete? Fuses tutorial-path membership, anchor-specific backlinks, transitive doc-level backlinks, and recent-edit recency into a single verdict (safe_to_delete, tutorial_path_blocking, anchor_referenced, backlinks_blocking, recently_edited_blocking) plus up to 5 ranked blockers and a one-line recommended_action. Read-only — never mutates the index.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"repo": "<repo>",
"section_id": "<section_id>"
},
"name": "check_section_delete_safe"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repo | Yes | ||
| section_id | Yes | Stable section ID, format owner/repo::doc_path::slug#level. v1.147+ — also accepts a `doc.md#anchor` reference to a heading written with an explicit `{#id}`. An ambiguous one is REFUSED (an `error` that sets `anchor_ambiguous`, `anchor_scope`, `anchor_match_count`, `anchor_candidates` (at most 20), `anchor_candidates_truncated` and `warning`), because the answer covers one section: pass a section id. | |
| recent_edit_days | No | Days within which a recent edit becomes a soft blocker. Default 14. | |
| transitive_depth | No | Backlink BFS depth. Default 3. |