GitHub Repo Manager — Full Assessment Mode

Orchestration layer — coordinates 9 assessment modules and produces the unified findings view.

Called by repo-manager/SKILL.md Step 7 ("proceed to assessment").

The unified findings format produced here is the authoritative presentation format — module

skills produce raw data; this skill owns the consolidated output. If the module execution

order changes, cross-module deduplication rules (Section 2) MUST be updated to match.

Architectural constraint: modules MUST run in the declared order (Security first) because

later modules defer duplicates to earlier ones. Reordering breaks deduplication silently.

Session context (established during onboarding, carried through all modules):

- tier (1-4): controls ceremony level, mutation strategy, staleness thresholds

- owner_type ("User" | "Organization"): controls which org-specific checks run

Org repos get: org inheritance resolution (community health), org ruleset audit (security)

User repos: org-specific steps are skipped; no behavior change for existing checks

Module Execution Order