Deep coherence review of a module. Usage: /review-module <module-path>

This command routes to the correct skill based on whether the target is a frontend or backend
module.

If $ARGUMENTS is empty, list available modules by scanning both directories:

- Frontend: `frontend/src/@aurora/modules/` and `frontend/src/app/modules/`
- Backend: `backend/src/@api/`

Show as a table with columns: Module, Project (frontend/backend), Path, File Count.

If $ARGUMENTS contains a module path or name:

1. **Detect the project** based on the path:
   - Path contains `frontend/`, `src/@aurora/`, or `src/app/` → Frontend
   - Path contains `backend/` or `src/@api/` → Backend
   - If just a module name (e.g., `countries`), search in both projects and ask the user to
     disambiguate if found in both

2. **Load the correct skill**:
   - Frontend → Read `frontend/.claude/skills/catalyst-review-module/SKILL.md`
   - Backend → Read `backend/.claude/skills/catalyst-review-module/SKILL.md`

3. **Execute the full review process** defined in the loaded skill against the target module

4. **Generate the audit report** in the format specified by the skill

5. **Ask the user** if they want to act on any of the findings

The module path can be:

- A full relative path: `frontend/src/@aurora/modules/common/countries`
- A short name that will be searched in both module directories: `countries`
- A backend path: `backend/src/@api/common/country`

This command performs a READ-ONLY audit. It does NOT modify any files.
