Map architectural gaps and produce an immunity plan with a Mermaid diagram.
npx skills add https://github.com/Trecek/useful-claude-skills --skill rectify-trecek
Please help me install this Agent Skill. Skill: rectify Source: https://github.com/Trecek/useful-claude-skills/tree/main/.claude/skills/rectify Command: npx skills add https://github.com/Trecek/useful-claude-skills --skill rectify-trecek
Deep investigation of test gaps and architectural weaknesses following an investigation, then devise a plan for architectural immunity rather than direct fixes. Use when the user asks to address root architectural causes after an investigation and to ensure issues are surfaced by testing rather than patched.
Initiate rectify after an investigation to map gaps and draft an immunity plan.
High-intent search queries and answers about installing and using this skill.
To map architectural gaps, analyze the investigation context using subagents to thoroughly map components and their interactions. This surfaces structural test gaps and patterns that allowed the bug to slip through, producing a documented immunity plan rather than direct fixes.
Architectural immunity planning is the process of analyzing systemic weaknesses post-investigation to change architecture, patterns, and contracts. It ensures future issues are surfaced by testing rather than patched, producing a detailed plan with a Mermaid diagram in a dedicated temp/rectify/ directory.
Create a test gap analysis plan by running a post-investigation session to outline an immunity-focused architecture. The process prioritizes architectural changes and pattern analysis over direct code fixes, generating a remediation plan and visual diagram without modifying source files.
Yes, architectural gap analysis requires a prior investigation session. It is applied after an investigation to document the context, map affected components and related patterns across the codebase, and craft an immunity plan rather than applying direct fixes.
The best way to prevent future test gaps is to architect immunity by changing patterns and contracts so issues become detectable by testing. Use subagents to map component interactions and generate a visual Mermaid diagram of the structural remediation plan.
Avoid direct code fixes during bug remediation when addressing root architectural causes after an investigation. Prioritize producing an immunity-focused architecture plan that makes future issues detectable by testing, ensuring systemic weaknesses are resolved rather than patched.
alastor0325Coordinate Firefox bug investigations and generate reproducible documentation.
tony30552001Review architecture, data flow, diagrams, edge cases, test coverage, and performance.
lucasgrowGenerate Mermaid diagrams for software architecture, data flows, and component relationships.
TalonT-OrgDesign architectural guards against identified bug patterns with detection scans and contract tests.
