code-review

mvskills integration

Read docs/agents/stack.md when present and load routed skills for affected apps. For the default NestJS profile, load nestjs-architecture for implementation and Standards review, nestjs-feature for feature work, and nestjs-cli for generators. Pass profile paths and skill entrypoints to workers. Matt's workflow owns orchestration; technical skills specialize execution. TDD, when selected, owns seam agreement and red/green ordering; refactoring belongs to the review stage.

Use the host's skill invocation mechanism; if no Skill tool exists read installed SKILL.md. Without subagents/worktrees execute the same stages sequentially, retaining separate Standards and Spec findings.

Pass applicable strict-typescript, react-architecture, design-system, api-contracts and docker-coolify entrypoints to the Standards reviewer for projects adopting those profiles. Check contract drift, boundary validation and runtime wiring in addition to static types; tooling-enforced rules remain the responsibility of the project's checks. Pass the selected profile entrypoints alongside every standards source discovered in step 3. Include agreed test seams and reported coverage limits for the reviewers; a fake-backed test must not be credited as proof of live wiring or persistence.

For UI changes, include any ui-ux-research note and the user's style decisions. Check that adaptations preserve the established visual identity unless a different style was explicitly requested. Review the recorded research/fallback evidence; Mobbin availability is optional and review alone does not require a new search.