القائمة
Use when exploring deployed SAP BTP CF app files, searching code (grep), viewing file contents, locating app roots, or inspecting runtime candidate lines through the cf-explorer CLI.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when indexing, linking, tracing, graphing, inspecting, diagnosing, cleaning, testing, or changing SAP CAP service-to-service flows with the service-flow CLI or @saptools/service-flow package, especially for multi-repository workspaces, SQLite state, handler implementation selection, runtime placeholders, dynamic targets, parser/linker evidence, and deterministic validation.
Use when a task involves running SQL, inspecting saved query refs, or discovering schemas, tables, and columns in SAP HANA Cloud databases bound to SAP BTP Cloud Foundry apps through the cf-hana CLI. Covers selector/app targeting, binding choice, read-only SELECT workflows, explicit writes, compact or structured output, saved result refs, and local result inspection.
Use when working with Jira Cloud through the jira CLI, including assigned issue lists, issue details with local inline image files, remote links, transitions, safe issue assignment, worklogs, descriptions, summaries, and comments.
Guide on how to remotely debug SAP BTP Cloud Foundry Node.js applications by combining deployed compiled JS discovery, Cloud Foundry log evidence, live HTTP request/response traces, runtime inspector snapshots, and read-only HANA evidence when debugging errors or exploring runtime behavior.
Use when analyzing SAP CAP CDS/HANA model structure with hana-lens, including building a compact CSN cache, fuzzy or regex entity search, field search, incoming reference lookup, dense entity descriptions, and safe association expansion.
Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
| name | cf-explorer |
| description | Use when exploring deployed SAP BTP CF app files, searching code (grep), viewing file contents, locating app roots, or inspecting runtime candidate lines through the cf-explorer CLI. |
Use cf-explorer to safely explore the files and code of a live SAP BTP Cloud Foundry app container. Prefer it when the task requires searching for code in a running app, inspecting configurations, locating where an app is deployed in the container, or getting context around a specific line of code.
If cf-explorer is missing, install it: npm install -g @saptools/cf-explorer.
--app is always required. --region, --org, and --space are optional and will automatically resolve if a current cf target is active. If the resolution fails (no target set), you must explicitly pass the full target. Note: there are no short flags (like -a); always use --app.cf-explorer automatically enables SSH and restarts the app when SSH is disabled.ls, grep, or view commands back-to-back, consider starting a persistent session to avoid the overhead of opening multiple SSH connections.--json is accepted as an explicit no-op and --no-json switches to human-readable output.cf-explorer reads the first/default app instance unless --instance <index> is provided.Discovery (Single-shot):
Find likely application root directories:
cf-explorer roots --app app-demo
List files under a directory:
cf-explorer ls --app app-demo --path /home/vcap/app
Search for a filename:
cf-explorer find --app app-demo --root /home/vcap/app --name "*handler*.js"
Search for text (grep) inside files:
cf-explorer grep --app app-demo --root /home/vcap/app --text "needle"
Read file context around a specific line (e.g., line 42 with 5 lines of context):
cf-explorer view --app app-demo --file /home/vcap/app/src/index.js --line 42 --context 5
Generate reusable file/line candidates for other tools:
cf-explorer inspect-candidates --app app-demo --text "needle"
Optional discovery parameters:
ls and session ls: add --pattern <pattern> to filter direct children by shell-style name pattern, for example --pattern "*helper*".grep and session grep: add --max-matches <count> to bound content matches. --include-files is accepted for parity with inspect-candidates, but grep output remains the content match list.find, grep, inspect-candidates, and their session variants: add --follow-symlinks when pnpm-style symlinked dependencies must be traversed.view and session view: use --context <lines> for surrounding lines; large contexts are allowed, but keep --max-bytes in mind for output size.Persistent Sessions (For repeated reads):
Start a session to keep the SSH broker alive:
cf-explorer session start --app app-demo
This returns a response containing a sessionId.
Reuse the session for fast reads:
cf-explorer session grep --session-id <id> --root /home/vcap/app --text "needle"
cf-explorer session view --session-id <id> --file /home/vcap/app/src/index.js --line 42
cf-explorer session stop --session-id <id>
cf target and didn't provide --region, --org, --space. Pass them explicitly via flags.--max-matches, --max-files, --max-bytes, or --timeout to adjust limits on broad searches. Pass --include-files only when the file candidate list is needed. Use --follow-symlinks for pnpm-linked dependencies and ls --pattern to narrow directory listings.--root path is correct (use roots command to discover it) and the --text is exact.