Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

cf-debugger

Sterne2

Forks0

Aktualisiert27. Juni 2026 um 01:31

Use when opening a Node.js inspector tunnel, debugging a SAP BTP CF app, or forwarding port 9229 from an app using the cf-debugger CLI.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

dongitran

dongitran/saptools

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Netzwerk- und ComputersystemadministratorenInformatik- und Mathematikberufe·SOC 15-1244

SKILL.md

readonly

name	cf-debugger
description	Use when opening a Node.js inspector tunnel, debugging a SAP BTP CF app, or forwarding port 9229 from an app using the cf-debugger CLI.

CF Debugger

Purpose

Use cf-debugger to open an SSH tunnel to a Node.js inspector for a Cloud Foundry app. This is useful for attaching a debugger (like VSCode or Chrome DevTools) to a running SAP BTP Cloud Foundry app. It automatically handles cf auth, enabling SSH if disabled, sending SIGUSR1 to the Node process, and setting up the port forward.

If cf-debugger is missing, install it: npm install -g @saptools/cf-debugger.

First Steps

Identify the app the user wants to debug. The app must be running Node.js.
An app selector (either <app> or <region>/<org>/<space>/<app>) can be used as a positional argument. If the bare app name is used, the CLI will try to infer the region, org, and space from the current cf target. If that fails, ask the user for the full target or pass them explicitly.
The debugger tunnel is persistent until stopped with cf-debugger stop.
Ensure the credentials (SAP_EMAIL and SAP_PASSWORD) are available in the environment to perform cf auth if needed.

Command Choice

Start a debug session:

cf-debugger start app-demo
# Or using the full selector if no current target is set:
cf-debugger start eu10/my-org/dev/app-demo

This will output the local port (e.g., 20142) that the debugger is forwarded to. The user can then attach their IDE to localhost:20142.

List active sessions:

cf-debugger list

Check the status of a specific session:

cf-debugger status app-demo

Stop a specific session:

cf-debugger stop app-demo

Stop all active sessions:

cf-debugger stop --all

Troubleshooting

Error: "No current CF target found": The user used a bare app name but hasn't run cf target recently. Use the full <region>/<org>/<space>/<app> selector.
Error: "SESSION_ALREADY_RUNNING": There is already an active debugger session for this app. Use cf-debugger list to see it.
Error: "SSH_NOT_ENABLED": The app or space doesn't allow SSH. Ensure that SSH is allowed at the space level and the CLI successfully restarted the app to enable it.
Error: "TUNNEL_NOT_READY": The app might not be a Node.js app, or the Node.js process didn't start the inspector when it received SIGUSR1. Verify the app is a Node app.

Mehr aus diesem Repository

gleiches Repository

service-flow

dongitran/saptools

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.

2026-07-142

cf-hana

dongitran/saptools

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.

2026-07-132

jira

dongitran/saptools

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.

2026-07-082

cf-remote-debug

dongitran/saptools

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.

2026-07-072

hana-lens

dongitran/saptools

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.

2026-07-062

agent-browser

dongitran/saptools

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.

2026-07-062

name	cf-debugger
description	Use when opening a Node.js inspector tunnel, debugging a SAP BTP CF app, or forwarding port 9229 from an app using the cf-debugger CLI.

CF Debugger

Purpose

If cf-debugger is missing, install it: npm install -g @saptools/cf-debugger.

First Steps

Identify the app the user wants to debug. The app must be running Node.js.
An app selector (either <app> or <region>/<org>/<space>/<app>) can be used as a positional argument. If the bare app name is used, the CLI will try to infer the region, org, and space from the current cf target. If that fails, ask the user for the full target or pass them explicitly.
The debugger tunnel is persistent until stopped with cf-debugger stop.
Ensure the credentials (SAP_EMAIL and SAP_PASSWORD) are available in the environment to perform cf auth if needed.

Command Choice

Start a debug session:

cf-debugger start app-demo
# Or using the full selector if no current target is set:
cf-debugger start eu10/my-org/dev/app-demo

This will output the local port (e.g., 20142) that the debugger is forwarded to. The user can then attach their IDE to localhost:20142.

List active sessions:

cf-debugger list

Check the status of a specific session:

cf-debugger status app-demo

Stop a specific session:

cf-debugger stop app-demo

Stop all active sessions:

cf-debugger stop --all

Troubleshooting

Error: "No current CF target found": The user used a bare app name but hasn't run cf target recently. Use the full <region>/<org>/<space>/<app> selector.
Error: "SESSION_ALREADY_RUNNING": There is already an active debugger session for this app. Use cf-debugger list to see it.
Error: "SSH_NOT_ENABLED": The app or space doesn't allow SSH. Ensure that SSH is allowed at the space level and the CLI successfully restarted the app to enable it.
Error: "TUNNEL_NOT_READY": The app might not be a Node.js app, or the Node.js process didn't start the inspector when it received SIGUSR1. Verify the app is a Node app.