scan
SolidScan project once per session. Run first — all other skills depend on this.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- datit309
- Repository
- datit309/supergraph
- Created
- 4 months ago
- Last Updated
- 6 days ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
project-scan
Use to scan the CURRENT project for latent, hard-to-track work — code TODO/FIXME, unchecked checklists and "pending/next steps" in docs, and plan/spec docs not yet tracked — then convert the chosen items into issues + a work plan on THIS project's board. Triggers — "escanea el proyecto", "convierte los pendientes en issues", "harvest backlog", "qué hay sin trackear", "arma el plan de trabajo", /scan.
scan
Full project dependency scan with live advisory fetch (OSV, NVD, GHSA) and EPSS exploit-probability + CISA KEV prioritisation. Covers npm and PyPI manifests + lockfiles. Use when the user wants thorough, up-to-date supply-chain CVE coverage for their project — but does NOT need system packages or IDE extensions (for those use `scan-full`).
cf-scan
Scan the project and populate memory (architecture, conventions, stack, features). Triggers: "scan the project", "scan the codebase", "bootstrap memory", "populate memory", "analyze the project". Token-heavy — always warn before proceeding.