dev-launch-file-browser

To launch a local file browser, invoke the dev-launch-file-browser skill to start the in-repo Filestash helper. It uses repo-owned wrapper scripts to run the web UI and reads connection details from the dockers/dev-helpers/filestash/.env file to report access URLs and credentials.

You can verify the local Filestash file browser by asking the skill to run its verification process. It executes the repo-owned verify.sh script, checks for missing-image expectations, and reports verification outcomes clearly without guessing ports or credentials.

Yes, you need both node and jq installed to run the Filestash docker helper. The skill explicitly checks for these prerequisites during startup and verification, surfacing a clear failure message if either dependency is missing instead of attempting to proceed.

To safely stop or reset the local file browser, trigger the skill's shutdown or reset functionality. It uses the repo-owned down.sh wrapper script to manage the helper lifecycle cleanly, preventing misconfigured ports and ensuring no custom Docker commands are needed.

Using a local file browser like Filestash is an effective way to inspect generated outputs during a development workflow. It provides a local web UI for quick repository file viewing and repeatable helper startup and shutdown management without requiring manual Docker commands.

The local file browser may fail to start if prerequisites like node or jq are missing, or if expected Docker images are not present. The skill surfaces these specific failures directly from the wrapper scripts without inventing ports or credentials to bypass configuration errors.