/sg-scout — GitHub Intelligence for ShipGuard

Scan the GitHub ecosystem for techniques that could make ShipGuard better. Parse repos, score relevance, extract actionable ideas, and file them as issues — or seed the techniques library for future reference.

Think of it as a research assistant that reads other people's code so you don't have to, then brings back only what's worth stealing.

Recommended model: a fast, capable model. Web search + repo scanning + summary writing is mechanical research work where a top-tier reasoning model provides no measurable quality gain. Prefer a faster model (e.g. /model sonnet) before invoking to conserve premium quota.

Preconditions

The publish phases require the ShipGuard repo checkout. Writing docs/scout-reports/, updating the techniques library, and filing GitHub issues only make sense inside the ShipGuard repository itself. Verify:

git remote -v | grep -q "bacoco/ShipGuard"   # or the detected ShipGuard origin

Anywhere else — the installed plugin cache, a host project — automatically behave as --dry-run: write the preview to visual-tests/_results/scout-report.md only, and tell the user why ("not running from the ShipGuard checkout, publishing skipped"). This check is applied at the start of Phase 5.

The research phases (1–4) can run from anywhere that has network access and an authenticated gh CLI.