Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

lxhkings/ShouldIPull

https://github.com/lxhkings/ShouldIPull · scanned 2026-06-17 01:58 UTC (1 month, 1 week ago)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · 0 actionable findings from 0 signal sources. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Active filters: excluding tests × Reset all

All 7 nodes from the latest scan, grouped by kind. Each node is a unit the engine identified (file, function, endpoint, table…). Most users won't need this view — it's primarily for debugging the engine's graph extraction or for AI agents that want to enumerate the project structure.

LabelLayerStatusPath
docs software healthy docs
superpowers software healthy docs/superpowers
specs software healthy docs/superpowers/specs
plans software healthy docs/superpowers/plans

LabelLayerStatusPath
2026-06-13-genshin-pull-decider-design.md software healthy docs/superpowers/specs/2026-06-13-genshin-pull-decider-desi…
2026-06-13-shouldipull.md software healthy docs/superpowers/plans/2026-06-13-shouldipull.md

LabelLayerStatusPath
lxhkings__ShouldIPull software healthy /data/fable5_failed_archive/lxhkings__ShouldIPull
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/5b6fc629-a04e-4ea8-a0af-d4707a1bf34c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/5b6fc629-a04e-4ea8-a0af-d4707a1bf34c/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.