菜单
Audit Delphi FMX source for cross-platform issues — Windows-only APIs, hardcoded paths, missing platform conditionals, mobile-incompatible patterns. Say "check this for Android/iOS", "is this safe on mobile/macOS/Linux", "audit for cross-platform issues".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Triage a Delphi FMX Android bug/crash from the PC over adb: capture logcat, pull the app's LightCore.ExceptionLogger log via run-as, classify the failure (SIGUSR1 IDE noise / Pascal exception / Java exception / native tombstone / deployment), symbolicate stripped-.so addresses against the linker .map (Tools\MapLookup.ps1), then root-cause and fix (build via light-compiler, never release). Use when the user says "/light-bug-Android", "the Android app crashes", "the app silently disappears on the phone", "triage this logcat", "exception class 10", or an FMX bug shows only on Android.
Diagnose and fix a Delphi bug end-to-end, however it arrived: a Thunderbird crash report (.mad), a pasted exception/stack trace, or a symptom described in plain words. Routes internally — a .mad or 'crash report' goes to the light-bug-MadShi pipeline, an Android-only symptom hands off to /light-bug-Android, everything else runs here: intake, reproduce (a failing DUnitX test preferred), localize, a MANDATORY derailment check before any fix, fix, then verify and compile (never releases). Use whenever the user reports a bug, crash, or unexpected behavior in a Delphi project — says "/light-bug", "/light-bug bionix", "I have a crash in program X", "the app does Y instead of Z", "this doesn't work", pastes an exception or stack trace, forwards a bug-report email, or describes an app crashing/hanging/misbehaving — even without typing a command.
Fix Delphi vocabulary and writing-clarity issues in Markdown docs — non-Delphi term swaps + bounded clarity rewrites. Say "check vocab", "fix vocabulary", "delphi terms", "clean up the md", or after writing/editing *.md in a Delphi project.
Audit Claude Code config files (settings.json, settings.local.json, .mcp.json) across the computer for unsafe or malicious content — hooks that run shell commands, credential/proxy env vars, arbitrary MCP servers, permission-bypass modes, over-broad allow rules. Classifies each finding DANGEROUS / SUSPICIOUS / SAFE. Read-only. Use when the user invokes `/light-security-ClaudeSettingsAudit`, says "check my settings.local.json for malware", "are my Claude permission files safe", "scan my Claude config", or "audit settings.json across the computer".
Summarize a YouTube transcript .txt file — cleans it first, then produces a structured summary (with a Delphi 13 / LightSaber adaptation section when the talk is about programming). Launches the light-web-YoutubeSummarizer agent. Use when the user invokes `/light-web-YoutubeSummarizer`, says "summarize this transcript", "what can I learn from this video for my Delphi work", or points at a file in c:\AI\Claude Code\Transcript\.
Pause mid-task and verify your own conclusions before continuing: classify every load-bearing conclusion VERIFIED / INFERRED / ASSUMED with evidence, actively attack the unverified ones, and find the earliest wrong turn if one exists. Not Delphi-specific — usable in any long or drifting task, in any language. Use when the user says "derailment check", "are you on track", "checkpoint yourself", "pause and check your conclusions", "/light-task-DerailmentCheck", or after any long autonomous stretch. ALSO fire this on yourself, unprompted, whenever: the user says "nope"/"no"/"wrong"/"stop" or otherwise corrects you; a fix didn't change the symptom; two fix attempts on the same problem both failed; you're editing a file your own analysis never mentioned; you're explaining away contradicting evidence instead of checking it; or you're about to act without ever having reproduced the problem.
| name | light-code-CheckOsCompatibility |
| description | Audit Delphi FMX source for cross-platform issues — Windows-only APIs, hardcoded paths, missing platform conditionals, mobile-incompatible patterns. Say "check this for Android/iOS", "is this safe on mobile/macOS/Linux", "audit for cross-platform issues". |
This is a thin launcher. Your only job is to resolve the input scope and launch the
light-code-CheckOsCompatibility agent. You do NOT audit the code yourself.
The argument is in $args. The user may pass a single .pas file, a folder, or several files.
Build the audit set:
<folder>/**/*.pas for the file list. If the result is large (more than
~25 files), tell the user the count and ask whether to audit all or narrow the scope..pas files with uncommitted changes. Run
git status --porcelain and keep the .pas files it lists (modified, added, or renamed) —
this is "the code I just changed". If that list is empty, ask the user which file or folder to
audit. Do NOT default to the whole repository.If the user names a target platform (Android, iOS, macOS, Linux), carry that into the agent's prompt so it focuses there. Print the resolved audit set as a short list before launching.
Call the Agent tool with subagent_type: "light-code-CheckOsCompatibility". Pass it the full audit set
in one prompt, plus any target platform the user mentioned. The agent reads the project
CLAUDE.md for the declared target platforms and intentional platform-specific code, scans the
files, and reports issues (Windows-only units/APIs, hardcoded paths, missing {$IFDEF} guards,
mobile-incompatible patterns).
Relay its final report to the user.
Print a short summary (the agent's full report is already in the transcript — do not re-paste it): how many files audited, how many issues by severity, and which need a human decision.