AGENT SKILL

dump-monitor

Use when checking SAP system health, investigating reported errors, or performing a periodic operational health check. Provides a standardized workflow using ListDumps/GetDump to detect ABAP short dumps and route new findings into PM triage for investigation.

License 许可
AGPL-3.0
最近更新
2026-11-14
Stars
★ 25
Forks
9

01 前言 Front Matter

name
dump-monitor
owner
devops-admin
scope
co-abap
status
active
version
1.0.0
metadata
{ "type": "core", "triggers": [ "dump-monitor", "ListDumps", "GetDump", "short dump", "system health" ] }
relates_to
[ { "type": "composes_with", "skill": "sap-fi" }, { "type": "composes_with", "skill": "sap-co" }, { "type": "composes_with", "skill": "sap-sd" }, { "type": "composes_with", "skill": "sap-mm" }, { "type": "composes_with", "skill": "sap-le" }, { "type": "follows", "skill": "abap-dev" }, { "type": "composes_with", "skill": "research-analysis" } ]
description
Use when checking SAP system health, investigating reported errors, or performing a periodic operational health check. Provides a standardized workflow using ListDumps/GetDump to detect ABAP short dumps and route new findings into PM triage for investigation.
last_reviewed
1786752000000
prerequisites
vsp MCP server

03 SKILL.md 正文

Dump Monitoring Workflow

Closes an observability gap: without this skill, ABAP short dumps are only found reactively when a user reports an error. Owned by DevOps/Admin (agents/devops-admin.md); any agent may run it as part of a health check.

When to Use

  • User asks for a system health check ("is anything broken", "check for dumps", "system status")
  • Before a release/transport window, as a pre-flight sanity check
  • Periodically, if the operator has wired this workflow into an external scheduler (see below)
  • After a user reports intermittent errors with no clear repro steps — check for a matching dump first

Workflow

1. List recent dumps
   ListDumps(since=<last-check-timestamp or 24h ago>)

2. For each new dump not already triaged (cross-reference against
   scratch/qa-reports/ or memory/ logs from prior checks):
   GetDump(dump_id) → capture: program, exception, call stack, timestamp, user/client

3. Classify
   - Runtime error in a Z*/custom object → candidate for PM triage (classification: "Debug")
   - Runtime error in an SAP standard object → note only, do not modify standard code
   - Repeated dump (same program/exception, multiple occurrences) → escalate priority

4. Route
   - New, actionable dump → hand to the PM with the note "Investigate dump: <program> — <exception>";
     the PM triage convention (not a registered command) creates the task file and dispatches investigation
   - Already-tracked dump → skip (avoid duplicate task files)

5. Record
   Append a Dump Monitoring Report (below) to the current session's memory/YYYY-MM-DD.md

Dump Monitoring Report Format

### Dump Monitoring — <date/time of check>

**Window checked**: <since timestamp> → now
**Dumps found**: <N> (<M> new, <N-M> previously triaged)

| # | Program | Exception | Timestamp | Occurrences | Action |
|---|---------|-----------|-----------|--------------|--------|
| 1 | ZCL_EXAMPLE | UNCAUGHT_EXCEPTION | 2026-07-10 14:02 | 3 | Routed to PM triage |

**Verdict**: <Clean / N actionable dump(s) routed to triage>

Scheduling Note

This harness has no built-in cron. To run this check periodically, wire an external scheduler (OS cron / Windows Task Scheduler / a CI scheduled workflow) to invoke the AI tool with a fixed prompt such as "Run the Dump Monitoring workflow from skills/dump-monitor/SKILL.md" — this keeps the mechanism portable across Claude Code, Gemini CLI, and Antigravity rather than tying it to one platform's session-level scheduler.

Related

  • agents/devops-admin.md — primary owner
  • PM triage convention (AGENTS.md §3.1 step 1) — destination for actionable findings (workflow convention, not a registered command)
  • skills/performance-tuning/SKILL.md — use together when a dump indicates a performance-related timeout

Context

This skill provides a standardized workflow for detecting and triaging ABAP short dumps in an SAP system. Without it, dumps are only found reactively when users report errors. The workflow uses ListDumps and GetDump to proactively identify runtime errors and route actionable findings into the triage process for investigation and resolution.

Execution Steps

  1. List recent dumps — Call ListDumps with a time window (default: last 24 hours or last check timestamp).
  2. Retrieve details — For each new dump not already triaged, call GetDump to capture program, exception, call stack, timestamp, and user/client.
  3. Classify — Determine if the dump is in a custom Z* object (actionable) or SAP standard (note only). Flag repeated dumps for escalation.
  4. Route — Actionable dumps are routed to the PM (triage convention) for investigation; already-tracked dumps are skipped to avoid duplicates.
  5. Record — Append a Dump Monitoring Report to the current session's memory/YYYY-MM-DD.md.

Output Format

A structured Dump Monitoring Report appended to the session memory log, containing:

  • Window checked (timestamp range)
  • Total dumps found and breakdown of new vs. previously triaged
  • Summary table with program, exception, timestamp, occurrences, and action taken
  • Overall verdict (Clean or N actionable dumps routed)

Related Skills

  • post-write-chain — QA gate that may catch syntax errors before they become dumps
  • abap-dev — Core development workflows that produce the code under observation
  • performance-tuning — Use in conjunction when dumps indicate performance-related timeouts

04 同仓库更多 Skills

5throck
5throck/ai-workspace-standards

i18n-layout

Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.

★ 25
5throck
5throck/ai-workspace-standards

i18n-layout

Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.

★ 25
5throck
5throck/ai-workspace-standards

i18n-layout

Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.

★ 25
5throck
5throck/ai-workspace-standards

i18n-layout

Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.

★ 25
5throck
5throck/ai-workspace-standards

i18n-layout

Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.

★ 25
5throck
5throck/ai-workspace-standards

i18n-layout

Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.

★ 25