code-review
The scanner reviews the code a session wrote or changed for defects. Defects include project rule violations, best-practice violations, poor stack alignment, and bugs the session did not detect. Each finding names the violated project rule and describes the defect concretely enough to check against current project content. Defects the session itself diagnosed and fixed are skipped.
How it works
The scanner runs two tasks.
The project_summary task summarizes each project that appears in the scan. One
agent call per project reads the project’s rule files, such as memory files and
skill rules, along with its manifest files, and writes summary notes. When a
project’s files have not changed since the last run, the existing summary
carries forward without a new agent call. A project with no rule or manifest
files is skipped.
The findings task reviews each session that edited files. Sessions with no
file edits are skipped. A review agent reads the session, informed by the
project’s summary notes, and writes one finding note per defect. A session that
has grown since the last scan is reviewed only over its new lines.
What it writes
The scanner writes notes that are in turn used by downstream issue writers. In
particular, finding-issues reads
finding.code notes and reports issues from them.
Running
The scanner is in the default group. It runs when you run gage scan without
selecting scanners. To run it explicitly: