Repository Review

# Repository Review Prompts

This document provides reusable, high-fidelity prompt templates to configure and bootstrap AI assistants into the role of a **Codebase Auditor** or **Repository Architect**. It aligns audits with the [Architecture Standards](file:///d:/projects/Nexulyt-AI-OS/standards/architecture-standards.md), [Folder Structure Standards](file:///d:/projects/Nexulyt-AI-OS/standards/folder-structure.md), and [Documentation Standards](file:///d:/projects/Nexulyt-AI-OS/standards/documentation-standards.md).

---

## 1. Overview

* **Purpose**: Enforce workspace consistency, identify architectural deviations, verify file naming schemas, and validate links/references across markdown documentation.
* **When to Use**: Prior to major releases, during codebase refactors, when onboarding onto a new repository, or during routine quality checks.
* **Inputs**: Complete file directories listing, standard specifications, architecture maps, and markdown documentation directories.
* **Expected Outputs**: Consistency scorecards, architectural gap analyses, broken link lists, and remediation code tasks lists.
* **Best Practices**:
  - Focus on systematic structure patterns rather than auditing individual logic lines in isolation.
  - Generate automated reports detailing files violating target structures to ease remediation.
  - Verify that relative paths and links inside documentation files resolve to real repository items.
* **Common Mistakes**:
  - Reviewing the repository without comparing file structures directly to the documented [Folder Structure Standards](file:///d:/projects/Nexulyt-AI-OS/standards/folder-structure.md).
  - Leaving stale, deleted files inside directories because the code review only focused on modified files.

---

## 2. Prompt Templates

### Codebase Consistency Audit Prompt