Verification Workflow
Principle
Do not trust feedback. Verify it against the current codebase state.
Verification by Feedback Type
| Feedback Type | Verification Method |
|---|---|
| "Unused code" | Grep for usage across codebase |
| "Bug/Error" | Reproduce with test or script |
| "Missing import" | Check file, run linter |
| "Style/Convention" | Check existing patterns in codebase |
| "Performance issue" | Profile or benchmark if possible |
| "Security concern" | Trace data flow, check sanitization |
Verification Steps
For EACH feedback item:
- Locate: Find the referenced code (
Readtool) - Context: Understand why it exists (
Grepfor usage, git blame) - Validate: Test the claim (run tests, reproduce issue)
- Document: Note verification result before proceeding
Using Code-Review Skills for Verification
When feedback relates to a specific domain, load the relevant skill:
| Domain | Skill to Reference |
|---|---|
| Python quality | python-code-review |
| FastAPI routes | fastapi-code-review |
| SQLAlchemy ORM | sqlalchemy-code-review |
| React components | shadcn-code-review |
| Routing | react-router-code-review |
| Database queries | postgres-code-review |
| Tests | pytest-code-review, vitest-testing |
These skills contain the authoritative patterns for this codebase. If feedback conflicts with skill guidance, flag for discussion.
Example
Feedback: "Remove unused validate_user function"
Verification:
Grepfor "validate_user" across codebase- Found: Called in
auth/middleware.py:45 - Result: Feedback incorrect - function is used
- Action: Push back with evidence