geo-infer-git
Git-based versioning and collaboration for geospatial datasets. Use when versioning spatial data, managing geospatial dataset lineage, tracking spatial data changes, resolving merge conflicts in geospatial formats, or building reproducible analysis pipelines.
Best use case
geo-infer-git is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Git-based versioning and collaboration for geospatial datasets. Use when versioning spatial data, managing geospatial dataset lineage, tracking spatial data changes, resolving merge conflicts in geospatial formats, or building reproducible analysis pipelines.
Teams using geo-infer-git should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/GEO-INFER-GIT/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How geo-infer-git Compares
| Feature / Agent | geo-infer-git | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Git-based versioning and collaboration for geospatial datasets. Use when versioning spatial data, managing geospatial dataset lineage, tracking spatial data changes, resolving merge conflicts in geospatial formats, or building reproducible analysis pipelines.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# GEO-INFER-GIT
## Instructions
### Core Capabilities
- **Spatial data versioning**: Track changes to GeoJSON, Shapefile, GeoParquet
- **Lineage tracking**: Dataset provenance, transformation history, audit trail
- **Collaboration**: Merge strategies for spatial data conflicts (geometry-aware diff)
- **Reproducibility**: Version-controlled analysis pipelines with spatial checksums
- **Branch strategies**: Feature-branch workflows for spatial analyses
### Key Imports
```python
from geo_infer_git.core.versioning import SpatialVersionControl
from geo_infer_git.core.lineage import DataLineageTracker
from geo_infer_git.core.collaboration import SpatialMergeEngine
from geo_infer_git.core.checksum import SpatialChecksumCalculator
```
## Examples
```python
from geo_infer_git.core.versioning import SpatialVersionControl
vcs = SpatialVersionControl(repo_path="./spatial_data")
vcs.track("boundaries.geojson")
vcs.commit("Updated county boundaries from 2026 census")
diff = vcs.diff("HEAD~1", "HEAD", file="boundaries.geojson")
print(f"Changed features: {diff.added + diff.modified + diff.deleted}")
```
## Guidelines
### Integrations
- Integrates with DATA for format-aware versioning
- Test: `uv run python -m pytest GEO-INFER-GIT/tests/ -v`