full-scan

Orchestrates seventeen Sokrates codebase scanners in dependency order and merges validated findings.

3|1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill full-scan-zeljkoobrenovic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: full-scan
Source: https://github.com/zeljkoobrenovic/sokrates-skills/tree/main/skills/scanners/full-scan
Command: npx skills add https://github.com/zeljkoobrenovic/sokrates-skills --skill full-scan-zeljkoobrenovic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a whole-codebase audit means coordinating many individual scanners in the right order, keeping their shared parameters consistent, validating each result, and merging everything into one report — doing this by hand is error-prone and slow. ## Core Features & Use Cases - Bundle Selection: Runs a basic scan (six descriptive scanners), a deep dive (all evaluative scanners or one family: quality, runtime, security), or a full scan of all seventeen, choosing a sensible default when the user is ambiguous. - Dependency-Ordered Execution: Runs scanners in waves so later scanners consume earlier findings, with parallel execution within a wave and graceful degradation when a predecessor is missing. - Merge, Render, and Diff: Validates each scanner's findings, merges them into combined-report.json, renders the AI Insights Explorer, and diffs against saved baselines on re-runs to surface what changed. - Use Case: Point it at an unfamiliar repository with a finished _sokrates analysis and ask for a full scan to get a baseline audit covering tech stack, functionality, architecture, security, testing, and more, with an interactive HTML explorer as the artifact of record. ## Quick Start Run a full scan of this repository using the existing _sokrates analysis and show me the combined report.

Frequently Asked Questions about full-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full codebase scan with Sokrates scanners?

Ask for a full scan on a project that already has a _sokrates analysis. The orchestrator runs all seventeen scanners in dependency order, validates each findings file, merges them into combined-report.json, and renders the AI Insights Explorer at _sokrates/reports/ai-insights/index.html.

What is the difference between a basic scan, a deep dive, and a full scan?

A basic scan runs six descriptive scanners that answer what the codebase is and does. A deep dive runs the evaluative scanners, either all of them or one named family (quality, runtime, security). A full scan runs all seventeen scanners for a complete audit.

Does the full scan require a Sokrates analysis first?

Yes, the target project must contain a _sokrates analysis, including config.json and the reports data archive. The orchestrator reads the config once, unzips the data to a scratch directory, and passes shared parameters to every scanner run.

How does a re-scan show what changed since the last scan?

Before overwriting, existing findings files are copied to a scratch directory as a diff baseline. After the new run, diff_findings.py compares old and new files per scanner, and the report leads with new, resolved, and changed items across scanners.

What happens if one scanner fails validation during a full scan?

A scanner that cannot pass validation ships with its unverifiable findings dropped or downgraded per the core rules; a failing file is never shipped. Missing predecessors are noted in the final report, and dependent scanners still run with graceful degradation.