post-run-validation
Sanity-check GIS outputs after an operation (row counts, extents, null spikes, geometry validity) and produce a confidence score.
- License 许可
- MIT
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- post-run-validation
- risk
- low
- domain
- geospatial
- source
- { "commit": "47afe3a4b5", "license": "MIT", "repository": "danmaps/gis-agent-skills", "imported_at": "2026-09-20" }
- license
- MIT
- version
- 1.0.0
- category
- geospatial
- platforms
- [ "claude-code", "cursor", "codex", "gemini", "antigravity", "copilot" ]
- subdomain
- general
- description
- Sanity-check GIS outputs after an operation (row counts, extents, null spikes, geometry validity) and produce a confidence score.
03 SKILL.md 正文
Post-run Validation
Close the loop after analysis or scripting. "No error thrown" is not validation.
Inputs
- Input dataset summary (name/path, feature count, extent, SR, key fields)
- Output dataset summary (same fields)
- Intended operation (buffer, clip, intersect, dissolve, join, routing, etc.)
- Optional: expected magnitude of change (e.g., "~same row count", "should shrink extent")
Checks (pick the ones that fit)
1) Basic counts
- Rows/features before vs after
- If output is 0 or massively smaller/larger than expected, flag
2) Extent + spatial reference
- Output extent overlaps input extent (unless expected otherwise)
- SR matches expectation; units make sense
3) Null and uniqueness spikes
- For key fields: null rate before vs after
- For IDs: uniqueness before vs after (did a dissolve/join duplicate or collapse unexpectedly?)
4) Geometry sanity
- Geometry type matches expectation
- Invalid geometry signals increased (self-intersections, empty shapes)
- Obvious topology smells (slivers after overlay, tiny polygons)
5) Field/schema drift
- Required fields present
- Unexpected field renames or type changes
- Domain/coded value preservation (if relevant)
Output
- Verdict: Pass / Warn / Fail
- Anomalies: bullet list with evidence (counts, % deltas)
- Confidence score: 0–100 with 1–2 sentence justification
- Next actions: what to inspect next (map view spot-check, sample records, rerun with env settings)
Tooling hints
If ArcGIS Pro context is available, use arcgispro_cli exports to ground the checks:
arcgispro layers --jsonarcgispro tables --jsonarcgispro status --json
If you can compute simple stats, prefer deterministic checks over vibes.
Example
User: "I ran intersect parcels x flood zones. Is it sane?"
Output: Warn (extent OK, SR OK, but output count is 5% of expected; null spike in APN; geometry sliver risk). Confidence 62/100.
04 同仓库更多 Skills
dei-assessment
Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.
dei-action-plan
Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.
culture-fit-assessment
Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.
cowork-to-code-bridge
Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.
counter-offer-response
Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.
continuous-feedback-system
Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.