Menu
Run full repo verification (lint, typecheck, test, security, diff review) and fix failures.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Audit documentation freshness — find docs that are stale or missing coverage for recent code changes.
Create a new Next.js API route with proper typing and error handling.
Add a new daemon REST endpoint with types, handler, web API proxy, and hook.
Create a new database service following the FXFlow pattern.
Wire a new WebSocket event end-to-end (daemon → types → hook → component).
Refactor code to meet file-size limits and DRY rules without changing behavior.
| name | verify |
| description | Run full repo verification (lint, typecheck, test, security, diff review) and fix failures. |
| disable-model-invocation | true |
Run comprehensive verification across the entire monorepo with a structured pass/fail report.
pnpm lint
If failures: fix the root cause, re-run until clean.
pnpm typecheck
If failures: fix type errors, re-run until clean.
pnpm test
If failures: fix failing tests, re-run until clean.
pnpm format:check
If failures: run pnpm format to auto-fix, then re-check.
Run these checks manually (grep/glob — no external tools needed):
Hardcoded secrets: Search all staged/modified .ts, .tsx, .js files for patterns:
OANDA_API_KEY, OANDA_TOKEN, FRED_API_KEY, ALPHA_VANTAGE_KEY, ANTHROPIC_API_KEY/[A-Za-z0-9]{32,}/ near key, token, secret, password assignments.env references hardcoded as string literals (not process.env.*)Console.log in production code: Search apps/ and packages/ for console.log( — flag any not inside test files (*.test.*, *.spec.*) or explicitly marked // keep: debug.
Webhook token exposure: Check that CF Worker webhook tokens are never logged or returned in responses.
OANDA credentials: Verify packages/db/src/encryption.ts is used for all credential storage — no plaintext API keys in DB service files.
If any findings: report them with file paths and line numbers. Fix critical issues (hardcoded secrets) immediately. Flag console.log instances for review.
If there are uncommitted changes (staged or unstaged):
git diff --stat to see scope of changesAfter all phases complete, output a structured report:
## Verification Report
| Phase | Status |
|----------------|--------|
| Lint | ✅/❌ |
| Type Check | ✅/❌ |
| Tests | ✅/❌ |
| Format | ✅/❌ |
| Security Scan | ✅/❌ |
| Diff Review | ✅/❌ |
**Verdict: READY / NOT READY**
### Findings (if any)
- [severity] description (file:line)
Only report "READY" when ALL phases pass with zero findings.