القائمة
Audit codebase architecture: module dependencies, layering, circular imports, ownership, and structural decay.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | brooks-audit |
| description | Audit codebase architecture: module dependencies, layering, circular imports, ownership, and structural decay. |
../_shared/common.md for the Iron Law, Project Config, Report Template, and Health Score rules../_shared/source-coverage.md for book-level coverage, exceptions, and tradeoffs../_shared/decay-risks.md for symptom definitions and source attributionsarchitecture-guide.md in this directory for the audit frameworkOnboarding mode: If the user asks for an onboarding report, codebase tour, or
"explain this codebase to a new developer", read onboarding-guide.md from this
directory and follow it instead of architecture-guide.md. This mode explains rather
than diagnoses — no Health Score, no Iron Law findings.
If the user has not specified files or a directory to audit: apply Auto Scope
Detection from ../_shared/common.md to determine the audit scope before proceeding.
Mode line in report: Architecture Audit
Create, repair, validate, visually QA, and package Codex-compatible v2 animated pets from character art, generated images, company or prospect brand cues, or visual references. Use for any new Codex pet, custom mascot, non-pixel pet style, brand-inspired pet, existing-pet repair, or 8x11 spritesheet workflow requiring all 9 standard animation rows, 16 look directions, deterministic assembly, QA artifacts, and spriteVersionNumber 2 packaging.
Rewrite current branch into N semantic commits with a legacy backup branch and optional rebase onto origin/main.
Merge origin/main into current branch while preserving branch intent, context, and ownership decisions.
Chain branch onboarding, code-health, and non-test analysis into a branch-scoped remediation plan.
Summarize current branch diff from fork point with intent, scope, risks, and context for follow-on work.
Assess tech debt and rank refactoring priorities, change pain, maintainability risks, and cleanup roadmap.