Audit proposed changes for failure modes using FMEA scoring.
npx skills add https://github.com/meaganewaller/.dotfiles --skill risk-audit
Please help me install this Agent Skill. Skill: risk-audit Source: https://github.com/meaganewaller/.dotfiles/tree/main/home/.claude/skills/common/risk-audit Command: npx skills add https://github.com/meaganewaller/.dotfiles --skill risk-audit
This Skill helps identify potential risks, failure modes, and edge cases associated with code changes or system modifications before they are deployed, ensuring production readiness and mitigating potential issues.
Use the risk-audit skill to audit the proposed changes for potential risks and failure modes.
High-intent search queries and answers about installing and using this skill.
FMEA risk assessment for code changes involves scoring failure modes by Severity, Occurrence, and Detection to calculate a Risk Priority Number (RPN). This process systematically identifies potential issues across data, availability, security, and operational domains before deployment.
A production readiness checklist is a pre-deployment validation tool used to ensure system stability and safety. You need it when modifying critical API endpoints to systematically verify that data, security, and operational requirements are met before shipping.
Identifying edge cases and silent failures in a code review requires analyzing input, state, and timing variations using structured matrices. This detects patterns that could lead to undetected errors and operational risks before merging changes.
Yes, you can quantify security audit risks by applying Failure Mode and Effects Analysis (FMEA) manually. This method assigns Severity, Occurrence, and Detection scores to calculate a Risk Priority Number (RPN) for identified threats without automated tools.
The best way to audit failure modes across data and integration domains is to perform a comprehensive risk assessment using FMEA. This approach evaluates potential disruptions across multiple categories and prioritizes them using calculated Risk Priority Numbers.
tranvietanh0Debate proposed software changes across architectural, security, performance, and UX domains.
SSiertsemaCompute FMEA RPN and Action Priority scores for process or design functions.
matteocervelliScan codebases for secrets, vulnerable dependencies, and insecure patterns.
TheBushidoCollectiveConfigure production Docker Compose stacks with security, health checks, and resource limits.
