/ 
Developer-Dashboard-3.26
/ which

NAME

which - private runtime command-inspection helper for Developer Dashboard

SYNOPSIS

dashboard which jq
dashboard which layered-tool
dashboard which alpha-skill.run-test
dashboard which alpha-skill.level1.level2.here
dashboard which --edit jq

DESCRIPTION

This private helper is staged under ~/.developer-dashboard/cli/dd/ so the main dashboard command can show the resolved runnable file and the participating hook files for built-in commands, layered custom commands, and dotted skill commands, or reopen the resolved command file through dashboard open-file when --edit is requested, without bloating the public switchboard.

PURPOSE

This staged helper exposes dashboard which, the command that explains what dashboard would execute for a given command token. It prints the resolved command file first and then every hook file that would participate for the same runtime resolution path.

WHY IT EXISTS

It exists because DD-OOP-LAYERS, staged built-in helpers, and nested skill dispatch can make command resolution non-obvious from the shell. A dedicated inspection helper gives users a direct way to confirm the exact file path and hook chain before they run a command.

WHEN TO USE

Use this file when changing dashboard which, the staged helper handoff, or the path and hook inspection contract for built-in commands, layered custom commands, and skill commands.

HOW TO USE

Users run dashboard which <target> where the target can be a built-in command such as jq, a layered custom command such as layered-tool, or a dotted skill command such as alpha-skill.run-test or alpha-skill.level1.level2.here. The helper prints one COMMAND line with the resolved executable path and then one HOOK line per participating hook file in runtime execution order. When users add --edit, the helper skips the printed inspection output and re-enters the public dashboard open-file command with the resolved command file path so the usual editor selection logic is reused.

WHAT USES IT

It is used by users debugging command resolution, by contributors verifying the switchboard remains thin, and by tests that lock down built-in, layered, and skill command inspection behavior.

EXAMPLES

Example 1:

dashboard which jq

Show the staged helper path for the built-in jq command and any layered hooks that would run before it.

Example 2:

dashboard which build-assets

Show the resolved layered custom command file and its participating hook chain.

Example 3:

dashboard which nest.level1.level2.here

Show the resolved nested skill command file beneath one installed skill tree.

Example 4:

prove -lv t/05-cli-smoke.t t/19-skill-system.t t/21-refactor-coverage.t

Rerun the focused tests that keep the staged helper and inspection behavior green after changes.

Example 5:

dashboard which --edit nest.level1.level2.here

Open the resolved nested skill command file through dashboard open-file instead of only printing the resolved path and hook chain.