Instruction file imported from stac-utils/pgstac (.github/instructions/scripts.instructions.md). Copyright stays with the author.

Build Scripts

Name: scripts
Author: stac-utils

See CLAUDE.md "Development Workflow" for usage. All scripts require the Docker compose environment.

runinpypgstac is the foundation — most scripts delegate to it
loadsampledata has a host wrapper at scripts/loadsampledata; prefer that wrapper over calling runinpypgstac directly
runinpypgstac uses the published-package path by default; set PGPKG_LOCAL_REPO_DIR to mount a local pgpkg checkout at /pgpkg when you need an override
scripts/container-scripts/ contains the in-container script payload copied into the pypgstac image; keep host wrappers in scripts/
stageversion modifies version files AND generates migrations — see CLAUDE.md "Migration Process"
stageversion regenerates *unreleased* migrations each run; if you hand-edit incremental SQL, rebuild the baked artifact with uv run --directory src/pgstac-migrate pgstac-migrate build-artifact and avoid rerunning stageversion unless you intend to overwrite edits
scripts/container-scripts/stageversion and scripts/container-scripts/makemigration now shell through pgpkg inside the container rather than assembling/diffing SQL directly
Set PGPKG_LOCAL_REPO_DIR on the host when you need to force a local pgpkg checkout for stageversion, makemigration, or related container-script testing
Tagged releases run .github/workflows/release.yml, which publishes pgstac-migrate and pypgstac-rs to PyPI via the GitHub pypi environment (and the Rust crate to crates.io); PyPI trusted publishers must exist for both projects
DO NOT run stageversion without understanding its side effects

{ "ocm": "1", "id": "stac-utils-pgstac-scripts-instructions", "kind": "skill", "name": "scripts", "description": "See CLAUDE.md \"Development Workflow\" for usage. All scripts require the Docker compose environment.", "publisher": "stac-utils", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "See CLAUDE.md \"Development Workflow\" for usage. All scripts require the Docker compose environment." ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/stac-utils/pgstac", "path": ".github/instructions/scripts.instructions.md", "ref": "a2a214b64c828abc4d5a2da2c95a4d9c02f34d59", "url": "https://github.com/stac-utils/pgstac/blob/a2a214b64c828abc4d5a2da2c95a4d9c02f34d59/.github/instructions/scripts.instructions.md", "key": "stac-utils/pgstac/.github/instructions/scripts.instructions.md" }, "applies_to": "scripts/**" }, "instructions": "# Build Scripts\n\nSee CLAUDE.md \"Development Workflow\" for usage. All scripts require the Docker compose environment.\n\n- `runinpypgstac` is the foundation — most scripts delegate to it\n- `loadsampledata` has a host wrapper at `scripts/loadsampledata`; prefer that wrapper over calling `runinpypgstac` directly\n- `runinpypgstac` uses the published-package path by default; set `PGPKG_LOCAL_REPO_DIR` to mount a local `pgpkg` checkout at `/pgpkg` when you need an override\n- `scripts/container-scripts/` contains the in-container script payload copied into the pypgstac image; keep host wrappers in `scr", "cost": { "context_tokens": 405 } }

scripts

About

Build Scripts

Use it

Manifest

Reviews