Run any Skill in Manus with one click

light-bug-bionix

Stars13

Forks1

UpdatedJuly 22, 2026 at 20:16

Alias for /light-bug-MadShi with the BioniX product preselected. Diagnose and fix a BioniX Wallpaper crash report from Thunderbird, then build (never release). Use when the user says "/light-bug-BioniX", "new BioniX bug report", "check the latest BioniX crash", or similar.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

GabrielOnDelphi

GabrielOnDelphi/Claude-Tools-for-Delphi

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	light-bug-BioniX
description	Alias for /light-bug-MadShi with the BioniX product preselected. Diagnose and fix a BioniX Wallpaper crash report from Thunderbird, then build (never release). Use when the user says "/light-bug-BioniX", "new BioniX bug report", "check the latest BioniX crash", or similar.
disable-model-invocation	true

/light-bug-BioniX — alias for /light-bug-MadShi bionix

This skill is a thin alias. The real pipeline is the light-bug-MadShi skill (the crash-report-specific pipeline; the general /light-bug skill routes there too, but this alias skips straight to it).

Do this:

Read c:\Users\trei\.claude\skills\light-bug-MadShi\SKILL.md and follow it exactly, with the product fixed to BioniX (the [BioniX] block in products.ini). Skip its "resolve the product" question — the product is already known.
If $args contains a path to an existing .mad file, pass it straight through to step 4 of that skill (hand off to the light-bug-MadShi agent with the BioniX profile). Otherwise run the list -> pick -> extract -> hand off -> relay flow for BioniX.

Everything else (mbox handling, candidate listing, the agent hand-off, the "do not release" rule) is defined in the general skill. Don't duplicate it here.

More from this repository

same repository

light-bug-android

GabrielOnDelphi/Claude-Tools-for-Delphi

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.

2026-07-2213

light-bug

GabrielOnDelphi/Claude-Tools-for-Delphi

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.

2026-07-2213

light-md-delphiidiom

GabrielOnDelphi/Claude-Tools-for-Delphi

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.

2026-07-2213

light-security-claudesettingsaudit

GabrielOnDelphi/Claude-Tools-for-Delphi

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".

2026-07-2213

light-web-youtubesummarizer

GabrielOnDelphi/Claude-Tools-for-Delphi

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\.

2026-07-2213

light-task-derailmentcheck

GabrielOnDelphi/Claude-Tools-for-Delphi

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.

2026-07-2213

name	light-bug-BioniX
description	Alias for /light-bug-MadShi with the BioniX product preselected. Diagnose and fix a BioniX Wallpaper crash report from Thunderbird, then build (never release). Use when the user says "/light-bug-BioniX", "new BioniX bug report", "check the latest BioniX crash", or similar.
disable-model-invocation	true

/light-bug-BioniX — alias for /light-bug-MadShi bionix

Do this:

Read c:\Users\trei\.claude\skills\light-bug-MadShi\SKILL.md and follow it exactly, with the product fixed to BioniX (the [BioniX] block in products.ini). Skip its "resolve the product" question — the product is already known.
If $args contains a path to an existing .mad file, pass it straight through to step 4 of that skill (hand off to the light-bug-MadShi agent with the BioniX profile). Otherwise run the list -> pick -> extract -> hand off -> relay flow for BioniX.

Everything else (mbox handling, candidate listing, the agent hand-off, the "do not release" rule) is defined in the general skill. Don't duplicate it here.