code-review

FoundationJIT only

analysis-agent/task-agent/review-agent: use when code needs correctness, security, performance, maintainability, or hallucinated-API review; skip when no review is needed.

Group: Engineering workflow
Supported roles: MainAnalysisTaskReview
Source: SKILL.md

Use when

Trigger signals that make this skill the right owner

review code for defects regressions contracts security performance maintainability readability structure quality side effect pollution weak signatures change locality cleanup debt

Do not use when

Anti-triggers — as binding as the triggers above

no task-local code review decision is required

Required inputs

What must be supplied before this skill can decide anything

current task contract
selected primary Professional Skill
task-local trigger evidence

Output contract

What this skill owes the next role

bounded review with inspected surface, contract and path evidence, actionable findings, consequence-based severity, proof limits, and non-blocking improvements

Escalation signals

When this skill must hand the decision back

Superficial review misses behavioral bugs hidden risk boundary pollution and maintainability defects that spread future changes

Loaded by

This skill never owns a task. These professionals may pull it in as Layer 3.

Targeted references

Each reference carries its own load condition. None of them enter context by default.

Reference	Load when	Do not load when	Required by
checklist.mddecision-checklist	Review spans contracts, security, resources, tests, or rollback risks.	The final diff changes no material behavior.	ReviewAnalysisTask
evidence-patterns.mdevidence-pattern	Approval depends on fresh diff, validation, and finding traceability.	No review verdict or non-finding claim is being issued.	ReviewAnalysisTask
finding-taxonomy.mdtargeted	Borderline findings require severity calibration or industry taxonomy.	Ordinary findings already have clear impact and severity.	ReviewAnalysisTask