Detect No-Go safety issues in firmware changes affecting BKIN/BKIN2, STO, timers, and watchdogs.
npx skills add https://github.com/AntonBespalov/WC_IST --skill strict-audit
Please help me install this Agent Skill. Skill: strict-audit Source: https://github.com/AntonBespalov/WC_IST/tree/main/.codex/skills/strict-audit Command: npx skills add https://github.com/AntonBespalov/WC_IST --skill strict-audit
Zero-tolerance risk management for safety-critical systems by enforcing No-Go audits that reveal blocking findings and required timing/fault-injection evidence before power-on or safety-critical changes.
Run the strict-audit assessment against the current codebase to determine PASS/FAIL with blocking issues.
High-intent search queries and answers about installing and using this skill.
To perform a No-Go safety audit, run an assessment against your codebase to detect blocking issues in safety-critical paths like BKIN/BKIN2 and STO. It outputs a clear PASS or FAIL status with actionable evidence and required timing measurements.
A No-Go safety issue is a blocking finding in safety-critical architectures that violates conformance to canonical documents like SAFETY.md or ARCHITECTURE.md. These issues involve timers, watchdogs, or fault-injection paths and must be resolved before power-on.
You need to run a safety audit on STO and BKIN paths before enabling the power stage or immediately after safety-related code changes. This ensures timing constraints and fault-injection evidence meet the zero-tolerance risk management criteria.
You can verify fault-injection tests and timing constraints by mapping findings to canonical safety documents and architecture constraints. The audit guides measurements using GPIO, oscilloscope traces, or fault-injection tests to provide traceable evidence.
No, the audit enforces conformance to SAFETY.md, PROJECT_CONTEXT.md, ARCHITECTURE.md, and TEST_PLAN.md. These documents are required to map findings to canonical safety constraints and provide traceability for blocking No-Go items.
Automated safety audits are limited to detecting No-Go issues in code changes affecting specified paths like timers, watchdogs, and safety hardware interfaces. They cannot replace physical measurements via GPIO or oscilloscope traces required for final verification.
AntonBespalovDocument a verification proof plan for STM32G4 welding firmware with FreeRTOS.
uzumaki-incDiagnose software bugs through a Phase 1-5 root-cause analysis workflow.
robertbr123Automate code review with security scans, quality checks, and automated fixes.
AminAlamDefine safe interrupt handling practices for medical device firmware.
