headless-ghidra-scope
Headless Ghidra Scope — P0.5
Deprecated compatibility-only alias. Scope selection is now part of P0 Intake; do not route new workflows here as a primary pipeline stage. Keep this document only for older CLI phase aliases or historical runs that still mention P0.5.
Required ghidra-agent-cli Commands
ghidra-agent-cli scope showghidra-agent-cli scope setghidra-agent-cli scope add-entryghidra-agent-cli scope remove-entryghidra-agent-cli gate check --phase P0.5
Inputs
artifacts/<target-id>/pipeline-state.yaml(from P0)artifacts/<target-id>/scope.yaml(initially empty from P0)- User guidance on what to analyze (function names, address ranges, symbols)
- Binary inspection results from
ghidra-agent-cli inspect binary
Outputs
- Updated
artifacts/<target-id>/scope.yamlwith non-emptyentries - Scope mode:
manual,auto, ormixed
Exit Expectations
scope.yamlhas a non-emptyentriessequence.- Each entry references a valid address, function name, or symbol.
- Compatibility P0.5 gate passes when older runs still require it.
Constraints
- Do not run Ghidra analysis or baseline export in this phase.
- Do not modify
pipeline-state.yaml. - Only use
ghidra-agent-cli scopecommands for scope mutations.
Next Step
- Compatibility P0.5 gate passes →
headless-ghidra-baseline
More from bytelandtechnology/headless-ghidra
headless-ghidra
Entry skill for the Headless Ghidra YAML-first reverse-engineering pipeline. Use when the user asks to analyze, decompile, triage, resume, or iterate on a binary target with Ghidra/headless-ghidra. Reads artifacts/<target>/pipeline-state.yaml, routes P0–P4 phase skills, runs gate checks, and manages review pauses. Performs zero analysis work itself.
36headless-ghidra-intake
P0 phase skill for Headless Ghidra intake. Use when a target binary/archive needs identity confirmation, workspace initialization, Ghidra discovery, binary inspection, or analysis scope setup before any Ghidra analysis runs.
35headless-ghidra-evidence
P2 phase skill for Headless Ghidra third-party evidence. Use after P1 to review baseline/runtime artifacts, identify or rule out third-party code, record pristine sources, classify functions, and capture evidence before metadata recovery.
35headless-ghidra-batch-decompile
P4 phase skill for Headless Ghidra selected function substitution. Use after P3 when an approved batch of functions should have metadata applied, be decompiled through Ghidra, and be recorded as per-function capture/substitution YAML.
33headless-ghidra-baseline
P1 phase skill for Headless Ghidra baseline and runtime evidence. Use after P0 when the target must be imported into Ghidra, auto-analyzed, exported to baseline YAML, and given reproducible runtime or hotpath observations without decompiling function bodies.
30headless-ghidra-discovery
P3 phase skill for Headless Ghidra metadata discovery. Use after P2, or after a P4 batch exposes missing context, to enrich function names, signatures, types, constants, strings, and hotpath metadata in YAML before serialized CLI apply.
30