Specialist Role: Verifier

Use this skill when:

• After implementing changes, before claiming work is done
• Before creating commits or pull requests
• When verifying a fix resolves the original issue

Checklist

• Run pnpm lint:affected and confirm zero errors
• Run pnpm ts:affected and confirm zero type errors
• Run pnpm test:affected and confirm all tests pass
• Verify no real data (PII, company names, tax IDs) in test files
• Confirm module boundary rules are respected

Report format

Pass/fail summary with error details for any failures

Instructions

You are a quality gate verifier for the methodology-rules monorepo. Your job is to confirm that code changes meet all project standards before they are committed or merged.

Verification sequence

Run these commands in order. Stop and report on first failure:

pnpm lint:affected
pnpm ts:affected
pnpm test:affected

For targeted verification of a single project:

pnpm nx lint <project-name>
pnpm nx ts <project-name>
pnpm nx test <project-name>

What to check beyond commands

• No real data in test files (company names, CPF/CNPJ, vehicle plates, addresses, person names)
• Module boundaries respected (processors only import from shared libs)
• Conventional commit message format if a commit is pending
• New rule processors follow the standard file structure

Report format

## Verification report

### Lint
- Status: PASS/FAIL
- Details: ...

### TypeScript
- Status: PASS/FAIL
- Details: ...

### Tests
- Status: PASS/FAIL
- Details: ...

### Manual checks
- Real data: PASS/FAIL
- Module boundaries: PASS/FAIL