RedHat Debugger

Diagnose failures using reproduce → isolate → fix → verify workflow.

Security Scan

This is an instruction-only debugging workflow that is internally consistent with its stated purpose; it requests no credentials or installs and contains no code, but you should avoid pasting secrets or sensitive logs when using it and verify the author/source if that matters to you.

Purpose & Capability

The name/description (debugging workflow) matches the contents: a step-by-step reproduce→isolate→fix→verify process. The skill declares no binaries, env vars, installs, or code, which is appropriate for an instruction-only debugging helper.

Instruction Scope

The SKILL.md instructs the agent to accept symptom, repro_steps, logs, and optional environment metadata. The instructions do not ask the agent to read system files, contact external endpoints, or access unrelated credentials, so scope is narrowly focused on debugging. Note: because 'environment' and 'logs' are permitted inputs, users must avoid providing secrets or sensitive production data in those fields.

Install Mechanism

No install spec and no code files are present. This is lowest-risk: nothing is written to disk and no external packages are fetched.

Credentials

The skill declares no required environment variables or credentials (proportionate). However it accepts an optional 'environment' input (the doc says 'no secrets'). This is reasonable for debugging, but the skill cannot enforce that users omit secrets — avoid sending API keys, tokens, or other sensitive data in the 'environment' or 'logs' fields.

Persistence & Privilege

always is false and the skill does not request persistent system-level presence or modify other skills. The default ability for the agent to invoke the skill autonomously is not by itself a concern here.

Assessment

This skill is an instruction-only debugging workflow and appears coherent and low-risk. Before using it: (1) do not paste secrets, API keys, or full production dumps into the 'logs' or 'environment' inputs — redact or sanitize sensitive data; (2) confirm the author/source if you require an official Red Hat integration (metadata claims 'RedHat Dev' but registry owner IDs differ in the included files); and (3) when applying fixes recommended by the skill, review and test diffs locally / in a staging environment before deploying to production.

SKILL: debugging

Purpose

Diagnose errors with a deterministic workflow: reproduce → isolate → fix → verify.

When to Use

• Tests are failing.
• Runtime errors occur (stack traces, crashes, misbehavior).
• Performance regressions or unexpected output is reported.

Inputs

• symptom (required, string): error message, failing test, or observed behavior.
• repro_steps (optional, string): how to reproduce.
• logs (optional, string): relevant logs/traces.
• environment (optional, object|string): OS, versions, env vars (no secrets).

Steps

1. Reproduce deterministically:
   • capture exact command(s)
   • capture versions
2. Localize failure:
   • narrow to smallest failing unit/test
   • add targeted logging/diagnostics if needed
3. Form hypotheses and test them one by one.
4. Implement the smallest fix that resolves the root cause.
5. Add/adjust tests to prevent regression.
6. Verify:
   • original repro no longer fails
   • related tests still pass

Validation

• Root cause is stated explicitly (not only the symptom).
• Fix is verified by test/repro.
• No unrelated behavior changes are introduced.

Output

root_cause: "<what broke and why>"
fix: "<what changed>"
verification: ["<commands/tests>"]
follow_ups: ["<optional hardening>"]

Safety Rules

• Do not “fix” by disabling tests or checks unless explicitly approved and justified.
• Prefer reversible debugging changes (guarded logs, small diffs).

Example

Symptom: “TypeError: cannot read property 'x' of undefined in production.” Output: root cause (missing null check), fix, and regression test.