red-team-review-welding

Identify failure scenarios, timing risks, and safety invariants in welding power supply code.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/AntonBespalov/WC_IST --skill red-team-review-welding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: red-team-review-welding
Source: https://github.com/AntonBespalov/WC_IST/tree/main/.codex/skills/red-team-review-welding
Command: npx skills add https://github.com/AntonBespalov/WC_IST --skill red-team-review-welding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Independent adversarial code review to identify failure scenarios, timing risks, and safety invariant violations in welding power-supply software after patches or PRs, focusing on finding issues and demanding evidence rather than rewriting code.

Core Features & Use Cases

  • Detect hardware path disable logic issues and verify alignment with welded safety core baselines.
  • Reveal timing races, RTOS scheduling pressures, ISR/DMA contention, and unsafe state transitions; require measurements and proof.
  • Produce a prioritized list of risks with reproduction steps, required tests or fault-injection scenarios, and recommended minimal fixes.

Quick Start

After applying patch or PR in a critical module, run the red-team review to generate a risk list and evidence requirements.

Frequently Asked Questions about red-team-review-welding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review welding power supply code for timing races after a patch?

Red-team review of welding power supply code identifies timing races and RTOS scheduling pressures after patches. It applies to critical modules, including 250 µs EtherCAT or 1 ms degraded fallback paths, to uncover worst-case behaviors and demand evidence.

What is a red-team review for welding power supply safety invariants?

A red-team review for welding power supply safety invariants is an independent adversarial code review. It detects hardware path disable logic issues and unsafe state transitions, verifying alignment with welded safety core baselines rather than rewriting code.

How do I generate fault-injection scenarios for PWM and ADC failure paths?

Generate fault-injection scenarios for PWM and ADC failure paths by running a red-team review after changes to fault paths. The review produces a prioritized risk list with reproduction steps, required tests, and recommended minimal fixes.

When do I need an adversarial review for EtherCAT and COMX ownership paths?

You need an adversarial review for EtherCAT and COMX ownership paths after any patch or PR changes timing, fault paths, or ownership logic. It targets critical modules to reveal ISR/DMA contention and requires measurements as proof.

Does this code review approach work without modifying the existing power supply codebase?

This review approach works without modifying the existing power supply codebase because it focuses on finding issues and demanding evidence. It outputs a prioritized list of risks with reproduction steps and proposed minimal fixes instead of rewriting code.

What are the limitations of using a red-team review for welding power supply software?

A limitation of this red-team review is that it does not rewrite code or fix issues directly. It only identifies and documents failure scenarios, timing risks, and safety invariant violations, requiring developers to implement the recommended minimal fixes.