architecture-self-healing

Detect architectural drift and propose remediation fixes across code and deployment artifacts.

Updated Apr 10, 2026

Search Tags:#architecture #remediation #drift #static-analysis #lint #self-healing

Ready to run

npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill architecture-self-healing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-self-healing
Source: https://github.com/majedsiefalnasr/bunyan-app-cursor/tree/main/.agents/skills/architecture-self-healing
Command: npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill architecture-self-healing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically detect, report, and guide remediation of architectural drift to keep software systems aligned with intended designs and governance.

Core Features & Use Cases

Automated drift detection across backend, frontend, and deployment layers with violation reports.
Propose compliant fixes and guidance to restore architectural conformance.
Validate fixes via static analysis and lint checks to ensure sustained alignment.

Quick Start

Review drift reports, apply the recommended remediation steps, and re-run analysis to validate the architectural alignment.

Frequently Asked Questions about architecture-self-healing

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

FAQPage Schema

How do I detect architectural drift in my codebase?▼

Architectural drift is detected by running static analysis across backend, frontend, and deployment artifacts to identify violations. The tool generates detailed reports highlighting non-compliant code and configuration segments.

What is the best way to remediate configuration and deployment drift?▼

Remediation involves reviewing generated violation reports and applying proposed fixes to restore alignment. You validate the remediated configuration and deployment artifacts by re-running lint and static analysis checks.

Can I use static analysis to enforce architectural governance across frontend and backend layers?▼

Yes, static analysis validates architectural conformance across frontend, backend, and deployment layers. It enforces governance by detecting violations and providing guidance to keep systems aligned with intended designs.

How do I validate fixes after remediating architectural violations?▼

You validate architectural fixes by re-running static analysis and lint commands on the updated code and configuration. This ensures sustained alignment and confirms that the deployed artifacts meet governance standards.

What types of deployment artifacts are checked during automated drift detection?▼

Automated drift detection checks code, configuration, and deployment artifacts across all layers. It applies static analysis to these artifacts to report violations and propose compliant fixes for sustained architectural alignment.

Why does my architectural lint check keep failing after applying proposed remediation steps?▼

Lint checks may fail if the applied remediation does not fully satisfy static analysis rules across all layers. Re-run the analysis to identify remaining violations in backend, frontend, or deployment artifacts and apply the remaining guidance.