stackhawk-data-seed

StackHawk Data Seed Skill

This skill produces checked-in, reproducible seed-data artifacts for a target repo so authenticated HawkScan finds non-empty results. The hawk perch seed command provides the deterministic steps — a static repo pre-flight (storage + upstream detection), a manifest validator, and an artifact finalizer. This skill supplies the reasoning between them: it reads the pre-flight's digest and designs the minimum seed manifest. It works the same across every agent that can run a subprocess and read its output.

It does NOT run the artifacts, start the environment, or write stackhawk.yml — those belong to the human, the user's tooling, and the hawkscan skill respectively.

---

When to Run

Invoke explicitly when:

• User says "set up data for HawkScan" / "seed this repo" / "my scan has no data to hit."
• Configuring HawkScan against a repo for the first time and the app needs authenticated routes to scan.
• A previous data-seed/ exists but the data shape changed (new entity types, new upstream service).

Do NOT run autonomously after code changes — this is a setup tool, not a per-commit safety net.

---

Phase 0: Preflight

0.1 — Confirm working directory

The user must invoke from inside the target repo (the repo HawkScan will scan):

test -d .git || echo "NOT-A-REPO"
pwd

If not a git repo, ask the user to cd to the target repo and re-invoke.

0.2 — Confirm hawk supports the seed flow (capability gate)

This skill drives the caller-driven hawk perch seed subcommands (validate and finalize). Probe for them directly:

# Identify the driving skill for CLI usage telemetry (read by hawk/hawkop).
export _STACKHAWK_SKILL=stackhawk-data-seed
if hawk perch seed validate --help >/dev/null 2>&1 && hawk perch seed finalize --help >/dev/null 2>&1; then
  echo "SEED-FLOW-OK"
else
  echo "SEED-FLOW-UNSUPPORTED"
fi
hawk version 2>/dev/null || hawk --version 2>/dev/null   # for the message only; never gates