Run comprehensive quality checks by orchestrating sub-skills.

Process

Identify context:

• If code changes are involved: run jj diff -s first to see changed files; then use jj diff -- path to restrict to specific files/directories

• If the user specified specific files or paths, focus on those

Run each of the following skills sequentially:

• Invoke 'code-review' skill (Full mode)

• Invoke 'code-verify' skill (Verify API usage against docs)

• Invoke 'code-test' skill (Run tests)

• Invoke 'code-lint' skill (Run linting)

Collect all findings

Consolidate findings into a single report

Output

• Summary - Overall code health assessment (including issue counts)

• Review Findings - From code-review (Critical, Quality, Security, Convention, Best Practices)

• Verification Findings - From code-verify (API mismatches or documentation issues)

• Test Results - From code-test (Test coverage, failures, and fixes)

• Lint Results - From code-lint (Auto-fixed summary and manual fix requirements)

• Action items - Prioritized list of fixes (Critical > High > Low)